💥 No Changeset

Latest commit: 28a85c8

Merging this PR will not cause any packages to be released. If these changes should not cause updates to packages in this repo, this is fine 🙂

If these changes should be published to npm, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

This shouldn’t be true and if it is then there’s a bug in emotion or your code. Do you have a reproduction and is this with next by any chance?

@mitchellhamilton my set up is pretty specific right now with Gatsby, but I'll try and get a small repo together to showcase it. It seems to make sense why I need it my case, but maybe I'm just doing something wrong 😅.

I create my own server using my cache from createCache:

export const {
  extractCritical,
  renderStylesToString,
  renderStylesToNodeStream,
} = createEmotionServer(cache)

And then in my gatsby-ssr file I import and use renderStylesToString:

import * as React from 'react'
import { renderToString } from 'react-dom/server'

import { ThemeWrapper } from './src/components/Theme'

import { renderStylesToString } from '../packages/server'

export const replaceRenderer = ({
  bodyComponent,
  replaceBodyHTMLString,
  setHeadComponents,
}) => {
  replaceBodyHTMLString(
    renderStylesToString(
      renderToString(<ThemeWrapper>{bodyComponent}</ThemeWrapper>)
    )
  )
}

I also have gatsby-browser setup as well:

import { ThemeWrapper } from './src/components/Theme'

export const wrapRootElement = ({ element }) => (
  <ThemeWrapper>{element}</ThemeWrapper>
)

Should I not have to do this? 🤔 If I don't use createEmotionServer it won't use my custom cache options that I set and it falls back to the default settings.

Gonna close this. @souporserious if you can get a reproduction, please open an issue.