Doesn't support SSR about react-refetch HOT 5 CLOSED

FWIW, I'm using this on a Next.js project, and was able to circumvent this error by including import 'isomorphic-fetch' in all of my connected components.

from react-refetch.

hmm, you didn't even get the Request error? Interesting. I'll try this again at one point. For now I was forced to move back to simply using await fetch().

@mattrothenberg Could you post a gist of your component? I do wonder how you've set everything up in terms of component functions and stuff. An example in the next.js repo under examples/ would be extra king, but too much work for me to ask you :D

from react-refetch.

Nope, no more request errors. As long as I include the following (in any connected component), I seem to be OK.

// UserList.jsx

import 'isomorphic-fetch'
import { connect } from 'react-refetch'

const UserList = () => <div>...</div>

export default connect(props => ({
  usersFetch: `/api/users/`
}))(UserList)

from react-refetch.

Okay. Since my import was import fetch from 'isomorphic-unfect' I'll close the issue for now and open it again if following your example doesn't work for me. thanks! :)

from react-refetch.

I actually came across the same issue today. You need Request and fetch on the global state for react-refetch to work on SSR. I don't use react-refetch on the server, because I need user credentials to make authenticated requests and I'm not going to implement a proxy for this. So my solution is very simple, I created a blocking ssr hoc:

// connect.js
import { connect } from "react-refetch";
const BlockSsr = Component => () => null;
export default (...args) => (process.browser ? connect(...args) : BlockSsr);

from react-refetch.