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...

I honestly can't give a different answer than before. Please create a runnable repro case to make it possible for me to dive straight into the problem.

*Disclaimer*: I'm not an RSC expert so take this with a grain of salt. > The next.js docs also state that https://github.com/mui/material-ui/issues/34905 and https://github.com/emotion-js/emotion/issues/2928 are also working on support Next.js...

> These are only the ones we specifically use, I don't know if we want to add a more comprehensive list, or perhaps do a filter like :(-webkit-:.*|-moz-.*|-ms-.*){ (though that...

My first thought is that something is tampering with your DOM. Are you able to reproduce this reliably?

Hm, it's quite interesting because `document.head` should always be available - even though `document.body` gets only available after parsing opening ``. You can take a look at this simple codesandbox...

@BtheGit can u share a repro case?

Just note that the presented solution works with the app directory - it still doesn't quite work with streaming. It's not exactly Emotion's fault though, other libraries won't work either...

To the best of my understanding - we should be able to support server components in the future. Some parts of that are fuzzy to me though. Mainly I'm not...

After talking with the Next.js team and helping them recognize the problem with `useServerInsertedHTML` and `Suspense` that issue has been fixed in https://github.com/vercel/next.js/pull/42293 With that fix Emotion roughly works in...