Anton Evzhakov

@bestander We use it in e2e-project which tests a group of packages which already have their own workspaces.

Hi @iMoses! It looks like the solution [doesn't work well](https://github.com/callstack/linaria/runs/8208055681?check_suite_focus=true#step:5:127). `"type": "module"` changes a lot in the way how that module should be written. Maybe we can change the type...

Hi @cojoclaudiu. I don't know. Maybe. We have [an example for Vite](https://github.com/callstack/linaria/blob/master/examples/vite/vite.config.js) (and I use Vite in my projects), and everything works well. Let's see how @iMoses's approach will affect...

@cojoclaudiu @iMoses I have fixed a couple of bugs with rollup@3 and the Vite example works well now. Could you please check this issue again?

@cojoclaudiu okay… I'll take a look later today.

Looks like we just need to rename all files in esm folders from `js` to `mjs`. Tomorrow I'll try to change the build system in order to support `mjs`.

@all-contributors please add @iMoses for code

Hi @kutnickclose! Thank you for such a great job! > 1. Would you be open to accepting two new packages (postcss-linaria and stylelint-config-standard-linaria) in the linaria monorepo or should they...

Hi @js2me For property based interpolations Linaria uses css variables. In your case, `var(--${props.color})` will be compiled as `var(--var(--some-generated-name))` that is just an invalid CSS syntax. There are at least...

Hi @nstepien! Thank you for your report. I fixed it in #1086 and will release in a couple of days.