Mateusz Burzyński

> I much prefer the cx() pattern from @emotion/css to the renderprops pattern from ClassNames. I guess my dream solution here would be for @emotion/react to export it's own cx...

While I understand that this has been a problem for you and that it's quite easy to get yourself into such a problem when using this matcher against pseudo-classes, I'm...

Documentation PRs are welcome as well 😉

> Calling css inside React.useMemo works but in my context I can't call css directly. It would be nice if you could shed some more details on that.

The problem here is that those components are being **remounted** (because they are virtualized). So using per-component cache won't solve anything. @m4theushw could you create a more compelling codesandbox that...

For reference - the repo for this is here: https://github.com/mitchellhamilton/emotion-benchmark-browser

When using `@emotion/css` you shouldn't try to use the cache directly - they are not linked together, because `@emotion/css` is completely decoupled from React. You probably either want `@emotion/css` +...

If you are using `@emotion/css` (and not `@emotion/css/create-instance`) then you should use `@emotion/server` (and not `@emotion/server/create-instance`). The linked documentation is slightly incorrect here - or is missing some important piece...

I can't reproduce this issue here: https://codesandbox.io/s/blissful-snyder-i5o6s?file=/src/App.js

> Hm, I reproduce the problem with that codesnadbox too, videos: I was testing on a different version on Safari. > styled-components version of that sandbox https://codesandbox.io/s/loving-lamarr-eyvpw?file=/src/index.js works as expected...