-
Notifications
You must be signed in to change notification settings - Fork 85
Hot reload doesn't work if webpack is running on different port than HTML page #170
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
Can you open a PR otherwise I’ll check in with webpack as it was added under their recommendations |
Why was that line added? It breaks HMR on many webpack setups.
It doesn't make sense, cause an
And on the other URLs |
This was a recommendation from webpack based on alternative types of links being added. open a PR and ill address it |
thinking on it more, it had to do for scenarios where the URL started with a hash, or basically wasn't a real link that went somewhere. base64 for example. You got a solution? |
For me removing this condition |
please do, I'm at work and legally cannot write the code, but I can merge yours. Ill also raise this with Webpack directly as I maintain both mini-css and extract css. |
PR created, I didn't bump the version, dunno what the policy is (some OS maintainers didn't like when the version is touched). |
No need to bump. We have system automation |
https://github.com/faceyspacey/extract-css-chunks-webpack-plugin/blob/master/src/hmr/hotModuleReplacement.js#L183
This checks makes CSS reload not work with webpack-dev-server running on a different port than the page.
Hot reload was working for me on v3.
Is there any way to override this check?
#161 is probably related
The text was updated successfully, but these errors were encountered: