-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Hot Module Replacement not working when target
is set to ['web', 'es5']
#2961
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
Comments
Yes, it is fixed in webpack-dev-server@4-beta.0 |
thanks @alexander-akait Is there a (draft) migration guide? I have a couple of devServer configs that are no longer supported in v4. |
What do you mean? How you run webpack-dev-server in this case? |
Eh, I just looked at the errors and took some guesses. BTW I'm running the server with the JS API not CLI. e.g. I'm getting |
Please read changelog many options were removed and it was described |
Thanks - somehow I missed it earlier. 😅 I fixed the config and HMR is working as intended. Thanks for your help! |
Operating System: macOS 11 / Windows 10
Node Version: v12.18.4
NPM Version: 6.14.0
webpack Version: 5.13.0
webpack-dev-server Version: 3.11.0
Browser: Chrome / IE11
This is a bug
This is a modification request
Code
Expected Behavior
Page should reload when files are changed.
HMR should connect via websocket
Actual Behavior
Not reloading. No message in the console either.
It seems websocket is not connected? I checked the Network - WS panel in Chrome devtools.
For Bugs; How can we reproduce the behavior?
When I use
target: ['web', 'es5']
, HMR doesn't seem to work. When I open the page I can see a[HMR] Waiting for update signal from WDS...
message but there is no second "[WDS] ..." (HMR enabled confirmation message). When I check the Networks tab in devtools, there are no WS connections.Curiously, when I change
target: 'web'
in the same config file - HMR works fine.The text was updated successfully, but these errors were encountered: