Mateusz Burzyński

An alternative solution to this has been merged in https://github.com/emotion-js/emotion/pull/2851

What browser are you using?

This might mean that you are using `babel-plugin-emotion` (v10) rather than `@emotion/babel-plugin` (v11). It's really hard to tell without a repro case but `@emotion/styled-base` is **nowhere** in the v11 codebase...

I see that you have done a little bit more than just checking out the progress 😉 Could we move those changes to a separate PR that would target this?...

We might be currently blocked on the `dtslint` update, see [here](https://github.com/emotion-js/emotion/pull/2543#issuecomment-974501224). I also mention in that comment that we might have to require at least TS 3.8 after this migration....

> TS does allow emitting multiple type declarations, each for a specific version, but I'm not sure it's viable. I'm not sure if emitting for specific versions is supported. The...

Ye, I'm not sure if it's worth it - I would probably consider doing this after the release, if we get some issue reports about this.

I understand that this is not the perfect answer to your problem but a workaround for the issue seems to be this: ```diff diff --git a/src/pages/_document.tsx b/src/pages/_document.tsx index ef8dfa2..01e82ff 100755...

> Is the DOM node switch for the style tag necessary for some reason? It feels like a strange way to handle inlining styles so I'm curious. I can imagine...

> I can see a next implementation in an old version of their example repo, so may move to that at some point. Right - this is using that "advanced"...