Webpack rebuilds, but dev server won't restart
See original GitHub issueAnyone having this weird problem? The hot reloading has been doing fine (other than occasional crash and somewhat slowness) until recently. Under npm run dev
, whenever a code change is made, webpack rebuilds, but the dev server on http://localhost:3000
won’t restart. In the console window, I only see
[1] [piping] File src\xxx.js has changed, reloading.
[0] webpack building...
[0] webpack built 97077085b02e470dd6b2 in 3465ms
But no
[1] ----
[1] ==> ✅ XXX is running, talking to API server on 3030.
[1] ==> � Open http://localhost:3000 in a browser to view the app.
Now the really weird thing is, if I just go ahead refresh the page, I’ll first get a ‘site can’t be reached’ error. But shortly after (2 - 5 seconds, maybe?), the dev server starts, and everything back to normal. It’s almost like the dev server went into hibernation and needs a request to wake it up.
My dev.config.js
is pretty much stock except devtool
is changed to cheap-module-source-map
. I’m running node v5.9.0 and npm 3.7.3 on windows 10.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:9
I’ve been seeing similar behavior as @realbugger, but the application server never successfully restarts. After changing a file, I see this:
Previously I would see this:
After a change and an unsuccessful restart, the application does not work correctly. API requests are not proxied to the API server, for one. A browser reload of any page triggers the restart of the application server and then things work.
After finding the issue below I locked piping to 0.3.0 and everything works:
https://github.com/mdlawson/piping/issues/15
It looks like the problem can be solved by upgrading piping package to the latest version (which is 1.0.0-rc.1 as of now). Please see #1068 for detail.