-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not use webSocketURL
#742
Comments
Support for this option have not been added, but should be. I'll try to find time to work on this. |
I'm pretty sure this is why I keep getting an error with websocket connection failure. Despite setting the react refresh overlay websockets. setting the dev-server host and the client websocket url details.
|
@pmmmwh Do you know where the plugin sends a the websocket connection request to webpack-dev-server, using the default |
I did a text search on GitHub for "ws" and I found this:
I'm not sure if this code needs to be changed |
//@ChocolateLoverRaj The urlParts.pathname actually does pick up the webpack websocketUrl config value. eg, hardcoding the urlParts.pathname into my desired format doesn't work.
It's very weird, in |
@Codex101 perhaps you need to set the port properly? |
Here is the docs for the option: https://webpack.js.org/configuration/dev-server/#websocketurl
This plugin just sends a request to
/ws
, even if a different path, hostname, or port is specified.Link to reproduce: https://github.com/ChocolateLoverRaj/webpack-dev-server-bug/tree/react-refresh#readme
The text was updated successfully, but these errors were encountered: