Use CRA's custom Webpack dev client #6
Comments
randycoulman
added a commit
that referenced
this issue
May 8, 2017
For now, we need to use the stock client because the custom dev client relies on `window.location` to find the dev server. However, since we host our apps inside a back-end app, the dev server is running somewhere else. See #6 for some ideas on how to go back to the custom dev client.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently use the standard webpack dev client because the custom client in CRA infers the protocol/host/port of the dev server from
window.location. However, since we host our React apps inside a back-end up,window.locationwill point at our backend server, not the webpack dev server.There are a few possible solutions to this:
Configure the backend app to proxy dev server requests to the actual dev server. See https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#proxying-api-requests-in-development.
Fork the react-dev-utils sub-project to make
webpackHotDevClient.jsconfigurable in some way (maybe using environment variables?).Wait for Adds HOST and PORT env variables to react app so websocket facebook/create-react-app#1588 to be merged.
The text was updated successfully, but these errors were encountered: