James Garbutt

this'll be because of rollup-plugin-postcss. by default it tries to inject the CSS into the `head` tag (see [here](https://github.com/egoist/rollup-plugin-postcss#inject)). im not too sure what the solution to this is. we...

Anidetrix/rollup-plugin-styles#200 is what we need fixing before its possible. basically rollup-plugin-styles and rollup-plugin-postcss are both hard-coded to assume the input is a CSS file. this means neither of them can...

vite falls over because it uses rollup internally, which uses `rollup-plugin-postcss`. That plugin doesn't yet support css-in-js properly via postcss' new features, i'll bump the issue over there to try...

@tomahl unfortunately it seems like it is stuck/stale. i do wonder if we should be moving more towards css imports going forward, but it does mean we'd lose the ability...

@ajbrun indeed it should be possible these days through import attributes i no longer recommend processing embedded styles in my own projects and my own team because of this. so...

in the projects i've used tailwind in, we basically split the styles out in all non-trivial cases i.e. we have this: ```ts // my-element.ts class MyElement extends LitElement { static...

minor update - just getting all the tests written for the new core, then will publish a pre-release of it and try it out here in this PR. once that's...

have published `postcss-lit@next` which seems to work! and came across some bugs i fixed while extracting all of this

postcss-lit likely won't work out of the box on styled-components (or at least not entirely). really we need a new postcss-styled-components syntax. i started creating one of those but didn't...

i see what you mean but i think you'd be getting into some really messy territory by doing that. as you'd require consumers to use your `html` rather than lit's,...