Mateusz Burzyński

My guess is that the problem is in this `compat` plugin: https://github.com/emotion-js/emotion/blob/1554a7e264e05780b2c5bd74ccb20a92005ba61d/packages/cache/src/stylis-plugins.js#L88 But I didn't yet analyze this in full. One alternative solution that I was thinking about (since adding...

Note that this might be prone to some edge cases but it probably shouldn't matter for real-life cases in which you are gonna use this.

After thinking about this a little bit - I think that a comment annotation would be the easiest solution for this. Something like: ```ts const Component = style('div')` color: black...

Yes, it's hard to say what's the **exact** bottom range - but I can say that I know companies using Emotion that have really high expectations about browser support. So...

At my previous job, we had to support IE11 too and Emotion was still working there just fine :)

Does this also happen in FireFox? If yes - would you be able to try recording a https://www.replay.io/ recording for me?

Well, this is... bizarre. After an hour of bisecting, refreshing, and hitting cache too many times I was able to reproduce this with just: ```js import { Global } from...

Those packages are community-driven from our perspective. We won't be providing any substantial changes to them ourselves - we welcome the community to prepare PRs though and we'll review them,...

> So as I see, at least, there is no way I can pass such props to child elements. It might be possible to call `React.cloneElement` with some extra props.

It’s probably because you usually want to have your own updater logic - like, u might want to switch between themes (light, dark, purple, whatever) but u dont literally want...