Allow hot reload sockPath to be changed

[brunomazzardo]

Is your proposal related to a problem?

Right now when using CRA behind a proxy, I can redirect all assets and bundle requests to some custom path, but the hot reload socket has a hardcoded path.

Describe the solution you'd like

Allow an extra option to be used, named equal to webpack custom socket pathname, sockPath, to be used by the developer. It needs to use WebpackHotDevClient.js, within react-dev-utils package and the sockPath config needs to be sent to webpack, on webpackDevServer.config.js

Describe alternatives you've considered

Nothing that I tried differently than changing the node_modules files worked

Additional context

I would be willing to implement this if the community feels like this will have so use for others than me.

[brunomazzardo]

@dmile Sorry to notify you from nowhere, but I saw you had a branch with a fix and was waiting to open a PR, care to revive the discussion? I think I will open a PR tomorrow with a possible solution, maybe you can check it and we can discuss it?

[dmile]

Hi @brunomazzardo!
Yep, same functionality discussed here. The fix is about reducing hard-code with socket path, by making it configurable. It adds a new functionality to project - that's why it not included to previous bug-fix. But I've tested a basic scenario - it works.

[heygrady]

This would be helpful. I’m working on a project where we proxy a path for multiple create-react-app instances (“/a” -> app a, “/b” -> app b). It would be helpful to be able to set the sockPath per app. Currently it’s impossible to develop more than one app at a time.