setting WDS_SOCKET_PATH does not fix what path the dev server responds on

[iamfrisbee]

If you run a simple npx create-react-app my-app and then try to start it with WDS_SOCKET_PATH=/somethingelse npm start the fast refresh won't actually work. In fact, the WS never responds. The solution that worked to fix this was:

1. First eject the app: npm run eject
2. Then edit the file /config/webpackDevServer.config.js and add webSocketServer: { options: { path: sockPath } }, to the configuration.

[jacobweberbowery]

Ran into this too — thanks for the workaround!

[doconix]

Also hit this bug when going through a proxy.
We haven't ejected but instead are using react-app-rewired to modify CRA's config.

We have WDS_SOCKET_PATH set in the environment, then in config-overrides.js, devServer section:

config.webSocketServer = config.webSocketServer || {}
config.webSocketServer.options = {
    ...config.webSocketServer.options,
    path: process.env.WDS_SOCKET_PATH,
}

[edit: to be clear, the above fix made hot-reloading work again]

[vasilev-alex]

I'm having the same issue. @iamfrisbee's solution worked for me

[tiredenzo]

+1