Skip to content
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

How to force reloading after build? #794

Closed
mnn opened this issue Feb 17, 2017 · 7 comments
Closed

How to force reloading after build? #794

mnn opened this issue Feb 17, 2017 · 7 comments

Comments

@mnn
Copy link

mnn commented Feb 17, 2017

After updating all packages the WDS no longer reloads after compilation. Is just prints to console Errors while compiling. Reload prevented.. How to disable this "feature" and force it to reload every time? (Compilation does contain errors, because of broken webpack and/or Awesome TypeScript loader. There is nothing I can do with that other than wait if someone after months finally take a look at it.)

@Arturszott
Copy link

Similar issue: webpack-contrib/eslint-loader#23

@mnn
Copy link
Author

mnn commented Feb 20, 2017

My "solution" is to down-grade before breaking change - to version 2.1.0-beta.9. It would be nice to have an option in WDS to disable this feature (misfeature for some).

@mribichich
Copy link

any news on this? is there a way to make webpack reload even though there are errors. I'm using typescript ts-loader and the errors should not stop the reloading

@mnn
Copy link
Author

mnn commented Jul 5, 2017

Both webpack and Awesome TypeScript loader are ignoring the issue. I see here is the same situation.

No love for TypeScript :-/. 👎

@shellscape
Copy link
Contributor

Closing due to issue age and inactivity. If anyone would like to put together and submit a pull request for this, we'd be happy to take a look at it.

@mnn
Copy link
Author

mnn commented Aug 10, 2017

Really? It is still an issue, we are not updating this package because of this "feature"... 😞

@shellscape
Copy link
Contributor

@mnn we're trying to get the issues queue under control so that we can effectively and efficiently address incoming issues. please remember that folks volunteer their time for the project. some pruning had to happen (and still needs to happen). closing this wasn't unreasonable, and if it gains traction we'd certainly reopen it. but the best course would be to open a PR for the feature.

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

4 participants