Mateusz Burzyński

Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the...

Did you perhaps forget to save your codesandbox? It's not using `@emotion/server` anywhere as far as I can tell.

@Jack-Works `CacheProvider` is using `value` prop (just like all Providers created using `React.createContext`) and not `cache` prop to accept a cache. When I fix this I get this output: >...

This is an interesting use case that might be worth supporting. While this is an interesting use case - it's also rather a niche use case. For that reason, I...

> Maybe createCache can receive the isBrowser from the options? It could but then we'd have to include all the related code in the "common path" and I'd like to...

I was also able to hack around `Global` issue: https://codesandbox.io/s/emotion-issue-template-forked-vec80x This could be used together with a bundler. You could create a custom module that would look something like this:...

Do you perhaps have a repro case?

Ah, yes - this is something that I've meant to mention here. That those presented workarounds only work in React 17 (well, the hack for `Global` should actually work everywhere)...

I mean that you can try removing such entries from our package.json files: https://github.com/emotion-js/emotion/blob/2d3d7dd1d8b0de9dbfd50e42ee716ac00fb70ecd/packages/react/package.json#L6-L9 Please note that even if you do so you would still have to execute `renderToStaticMarkup`/`renderToString` in...

> the basic flow is that the library gives us a callback that we return html from. that callback happens synchronously. so I don't think we could move it into...