Skip to content

Removing and readding entry point makes the server explode #270

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

Closed
SimenB opened this issue Sep 17, 2015 · 1 comment
Closed

Removing and readding entry point makes the server explode #270

SimenB opened this issue Sep 17, 2015 · 1 comment

Comments

@SimenB
Copy link
Contributor

SimenB commented Sep 17, 2015

At the moment, I'm moving between branches Where the entry point has moved on one machine. If I move to a branch where the files is not in the location provided to webpack-dev-server, I get Module build failed: Error: ENOENT which is fine. But if I move back to the original branch, it doesn't pick up on the fact that the file exists, I have to restart the dev-server.
This is a problem as I have to rebase against a changing base all the time, and it dies. I have no idea if it's actually fixable, though.

@SpaceK33z
Copy link
Member

SpaceK33z commented Sep 10, 2016

I doubt if this is something we can fix in webpack-dev-server. webpack takes care of building these files, not the dev-server. We might implement live-reloading for the webpack config and content base, which would (maybe?) fix this problem; #440 and #350.

Closing for now, but feel free to comment and I can always reopen it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants