-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
stat options not working in 2.1.0-beta.11 #697
Comments
To disable browser logs you'll need to use Sidenote: |
Having looked at the commit, I've made the same change locally so that I can at least use it. The annoying part is that this new behaviour stops all reloads for me (warnings didn't stop earlier versions from reloading so never really bothered) |
Yeah true. Currently that is done on purpose, but perhaps I should change that behavior a bit so that when you use |
Thanks @SpaceK33z for amazingly fast response!! Actually I would not normally want the warnings to disappear but not having a reload defeats the whole purpose of dev server. For what I gather it makes sense not to reload with errors, but my warnings are all about innocuous linting issues. In my case it would be better to reload with warnings like in older versions. Has this actually changed? |
Ahh okay, you're right. It should reload for warnings. I'll fix that soon. Is your issue fixed after that? |
Yes!! Thank you so much!! I wouldn't expect dev server to sort my warnings too!! 😂 |
Fix released in v2.1.0-beta.12. |
I'm submitting a bug report
webpack and webpack-dev-server version:
webpack: 2.1.0-beta.26
webpack-dev-server: 12.1.0-beta.11
Please tell us about your environment:
Linux
Running server via Node.js API
Current behavior:
I have the following in my config
And despite having turned all options warning still output to console in browser. This is annoying because linter warnings would stop the reload.
The terminal output is as it should though
Expected/desired behavior:
No output to console in browser with this config. Same as with terminal
The text was updated successfully, but these errors were encountered: