document is not defined with react-on-rails

[brandoncc]

Current behavior:

The documentation says that server side rendering works with no configuration needed if you install @emotion/core in a React app. I am getting document is not defined during the SSR.

I am using @emotion/styled, not css or jsx, I'm not sure if that could be where my problem is?

import * as React from 'react';
import styled from '@emotion/styled';

const Container = styled.div(
  {
    marginTop: 6,
    position: 'relative'
  },
  props => props.css
);

The error looks to be coming from a createCache method.

To reproduce:

I can create an example app if needed but I don't have one handy.

Expected behavior:

The page should render.

Environment information:

• react version: 16.8.0
• emotion version: 10.0.10

[Andarist]

How so you build your server? Webpack?

[brandoncc]

Yes, using webpacker via rails

[brandoncc]

I saw the other issue about cache breaking some static site generators....I don't think I have the same problem though. I have two bundles, one if which is for the server and uses renderToString. That is where I am having this error.

[xtroncode]

I am facing the same issue with ReactJS.net

[Andarist]

You should use target: ‘node’ in your webpack config

[brandoncc]

I don't think I can change that with webpacker :-/

[brandoncc]

Also, my code is running in the browser except that one bundle, don't I want it targeting the web?

[Andarist]

Well, I dont know how your bundles are structured - but in general client-side bundles are not the same as your SSR entry point, so you should have 2 separate builds.

[Dangoo]

@Andarist I have a similar issue, but I'm forced to use target: webworker in order to deploy my code to cloudflare. In that mode neither document nor process are allowed.

Maybe also related: #1246

[Andarist]

If you specify target as webworker the bundler should use default entries which have document access guarded.

If this is not working properly you would have to prepare a repro case that would showcase the behavior and which would be easy to investigate.

[Andarist]

Closing this because we have not received a repro case since September. It's also definitely a problem with used tooling or its configuration - not something we can fix in Emotion.