-
Current behavior: We are using a custom In development mode, this works great, I see zillions of To reproduce:
Expected behavior: I expect the Environment information:
|
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 14 replies
-
In production, Speedy mode isn't as convenient for debugging style issues which is why it's not enabled by default in development. If you want to disable speedy mode all together, you can do |
Beta Was this translation helpful? Give feedback.
-
Interesting, that fixed it, thank you @srmagura! Might I suggest some docs on Also, as prerendering is still a popular way for SPAs to satisfy SEO requirements, styles in the head are necessary for this, and many folks familiar with traditional css-in-js are probably accustomed to styles being injected into the head, this new-ish implementation comes as quite a surprise. I completely understand that Thanks! |
Beta Was this translation helpful? Give feedback.
-
I'm using the This also breaks in production, the styles are missing from the opened window. It seems I can fix it as suggested above by setting |
Beta Was this translation helpful? Give feedback.
-
For some reasons In I am using |
Beta Was this translation helpful? Give feedback.
In production,
@emotion/sheet
uses "speedy mode" which puts up to 65,000 style rules in a single style tag. They are inserted directly via the CSSOM rather than adding the CSS text to the inside of the<style>
tag.Speedy mode isn't as convenient for debugging style issues which is why it's not enabled by default in development.
If you want to disable speedy mode all together, you can do
createCache({ key: 'sarink', speedy: false })
. This will decrease performance of course so I would not recommend it.