Mateusz Burzyński

Thank you for the issue - TIL about constructable stylesheets (I knew there was such a thing for Shadow DOM but never occurred to me that I could use it...

> When updating a React component that has css passed through props which have dynamic content (i.e. not flattened by babel)? The problem is that `css` styles are never removed...

We don't plan to remove it right now but we think it's a really quirky API and that you should avoid using it. It's much better to compose things in...

I don't fully understand the latest problem mentioned here - could you prepare a codesandbox that would illustrate the problem?

With https://github.com/emotion-js/emotion/pull/2819 we are allowing ourselves to add a special entrypoint for workers. So we are able to fix this if somebody would be willing to provide a fix for...

This sounds like an issue with Storybook (since it's still on Emotion 10). Not much that we can do about it here.

Huh, interesting that you don't face this issue with a slightly older v11 version. I would have assumed that this is an issue with any v11 version.

You can fix most Storybook-relates issues with such config: ```js // ./.storybook/main.js module.exports = { // ... webpackFinal(config) { delete config.resolve.alias['emotion-theming']; delete config.resolve.alias['@emotion/styled']; delete config.resolve.alias['@emotion/core']; return config; }, }; ```...

> If I have @emotion/css as a dependency (which I do because I need to disable speedy for puppeteer/prerender.io runs) Well, this alone doesn't sound completely right. You do not...

Ye, this is definitely something I'd like to do in Emotion 12 but I'm also unsure when that will actually happen. Perhaps when we implement better support for React 18...