ESlint errors clutter browser console

[webpack-contrib]

ESlint errors clutter browser console

[josephfinlayson]

I'm happy with stderr and also I have a growl plugin. I just don't want them to be in my chrome console :)

[jikkujose]

Anyone has a solution for this. I seriously don't understand how someone thinks its a good idea to pollute the already small browser console with liniting warnings! Disabling the loader completely is to stop those warnings defeats the whole purpose.

[aamirshah]

The solution is: --client-log-level none

https://webpack.js.org/configuration/dev-server/#devserver-clientloglevel

[MoOx]

Webpack handle the output. This loader only emits eslint results. Why do you want to use this loader if that's not to see the errors?

[MoOx]

Oh you mean browser console. Ok then it's definitely something to handle in webpack configuration (and I have no idea how).

[josephfinlayson]

Thanks for the quick response. I hope someone sees this and can help!

[MoOx]

Maybe you can ask in webpack repo or gitter chan.

[nkbt]

I reckon it is a good thing that makes you fix your lint errors ;)

[sdtsui]

@josephfinlayson please reference the issue in webpack if you get help for this. I'm also interested.

I have this package as part of our build process. Overall, it's great. Would love it if our browserSync + webpack hot reload setup did not render the errors from eslint-loader, and simply output them to terminal.

[MoOx]

Not an eslint-loader issue, closing.

[stevenmusumeche]

I have the opposite problem. My eslint errors are not displaying in the browser console but I want them to.

[MoOx]

@jikkujose it's a webpack configuration from what I know. Please check webpack issue tracker.