-
-
Notifications
You must be signed in to change notification settings - Fork 133
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
Webpack HMR Support #716
Comments
inspecting the cli code, to get it to work you should set edit: it fails to update my html (although the console shows me that edit2: I think this works when you actually use more than 1 module. |
This works for me as long as I use Chrome. Thanks very much. How to run HMR should be include be included in the docs somewhere as it's a pretty cool feature. |
I am closing this as resolved. |
It will do a full reload rather than do a hmr when using with
|
@JeroenVinke should this be reopened for the open issue described above? or create a new issue? It's unfortunate that hmr is broken for app.html.
|
@kayle I believe this issue is relevant: aurelia/hot-module-reload#9. It’s not something we can fix in the CLI so the hmr repo seems like the best place |
Is HMR now supported with Webpack 3 support?
I created a test project with VS17+aspnetcore 2.0+ webpack. It does automatically pack on detected changes, but the changes don't show up on the browser.
I asked this question on S.O. here
I'm submitting a feature request
major.minor.patch-pre
Please tell us about your environment:
Operating System:
Windows 7
Node Version:
6.2.0
NPM Version:
3.8.9
Browser:
Chrome
Language:
TypeScript
Current behavior:
The webpack bundles are automatically recompiled on changes, but the changes don't propagate to the browser.
Expected/desired behavior:
HMR Support
What is the expected behavior?
Automatic updates in the Browser without refresh
What is the motivation / use case for changing the behavior?
Ease/speed of developement
The text was updated successfully, but these errors were encountered: