-
Notifications
You must be signed in to change notification settings - Fork 105
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-dev-server stops picking up changes. #30
Comments
Cc @rtfeldman I think this problem is because we need to update the npm version, should be fixed in master. @sircharleswatson could you confirm this by cloning this repo, then running the test project and attempting to reproduce there? |
👍 Published a new release to npm. @sircharleswatson can you reopen this and ping me if you can still reproduce this in v1.1.2 of |
@rtfeldman Proposing a reopen. I updated to 1.1.2 and it works after errors about 3-4 times and then it stops reloading :/ |
👍 thanks @sircharleswatson - not sure what he problem might be, though... |
@sircharleswatson Can you ping me on slack about this? |
Just my feedback: I had the problem on 1.1.1 and it's fixed to me on 2.0.0 |
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. |
@stevenleeg I have the same issue. Did you fix it since? |
Unfortunately not :( it was actually one of a few reasons I ended up switching off of elm for a small project. |
Yeah, understandably so, it makes it such a drag! I'll try write in slack for help 😭 |
Hi, 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.jsThe text was updated successfully, but these errors were encountered: