-
Notifications
You must be signed in to change notification settings - Fork 430
Components not reloading #89
Comments
same issue on windows. to take this one step further, I've never managed to find a boilerplate that works using webpack with dev/hot middleware. i've been working around this problem because I luckily managed to make webpack-dev-server at some point work in my project, so I made as much front-end as I could without needing an actual server. now that I need an actual server, I'm pretty much stuck :) |
Same here, just dose not work, haw to manually reload to see changes. |
solved this after many days of issues by completely removing node and npm and reinstalling you should look up an OS specific guide to ensure you clean out all lingering files. fixed problem for me on windows. gl |
I just created my own boilerplate, and and it works. I don't think there is anything OS specific, just some small bug. |
I too am having this problem... Running Windows 10 64-bit and node 4.1.1, will do as suggested above and try again. In the browser (Chrome) I can see that __webpack_hmr is being called, and i've also modified the code to console log, and it is getting to the event stream handler, but not sure what goes on after that. But Chrome looks to be timing out the request after approximately 20 seconds of no response. |
Looks to be more in line with this problem: webpack-contrib/webpack-hot-middleware#36 |
I'm having the same issue, could it be this: webpack/webpack#675 |
Thank you! |
Hi, is something broken with the current build?
The components display and it says HMR connected in the console but there is no hot reload (even after page refresh).
I tried adding 'webpack-hot-middleware/client?reload=true', to the entry, but that didn't help either.
Running this on a Mac
The text was updated successfully, but these errors were encountered: