webpack-dev-server stops picking up changes.
See original GitHub issueHi, I’m not sure what’s wrong but if Elm runs into an error and it can’t compile, it seems that webpack stops picking up changes after that. This happens with the elm-webpack-starter webpack.config and any other ones I try with elm + webpack. Any thoughts?
You can see my current webpack.config.js
here: https://github.com/sircharleswatson/elm-architecture-hop/blob/master/webpack.config.js
Issue Analytics
- State:
- Created 8 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
webpack-dev-server does not watch for my file changes
The gist is if your project folder is in a symlinked folder, detecting the file changes may not work on OS X. Previously,...
Read more >webpack-dev-server stops watching files for changes on .js ...
webpack-dev-server stops watching files for changes on .js syntax error #3175 ... I can try to mock something up but will take some...
Read more >Why webpack-dev-server Live-Reload Is Not Working - Medium
Manually reloading the web page picks up code change. webpack-dev-server works great but how can I make it work in production?
Read more >Development | webpack
Let's set it up: npm install --save-dev webpack-dev-server. Change your configuration file to tell the dev server where to look for files: webpack.config.js...
Read more >Solution for Webpack 5 Dev Server Not Live Reloading
There is currently a bug with Webpack 5 and webpack - dev - server not working that is caused by the existence of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is this fixed for everybody still? I’ve been seeing the same behavior on 3.0.6. The first error message will show up just fine, but any subsequent errors are ignored (forcing me to ctrl-c and re-run webpack to see the next error).
What’s interesting is that if I see an error, fix it, and there aren’t any new errors it will successfully compile without having to restart webpack.
Any ideas as to what could be going on here? I’m more than happy to provide more information if it’ll help.
Yeah, understandably so, it makes it such a drag! I’ll try write in slack for help 😭