Add option to control browser log level

[SpaceK33z]

Previously, when you used quiet: true or noInfo: true via the Node API or CLI, this only had effect on the output in the terminal (issue #109).

With this PR, these settings will be respected in the browser console as well.

Maybe it would be more flexible to add a separate option for this, but this would also mean more configuration. Looking for feedback on this.

[SpaceK33z]

To test this:

Add this to your package.json:

"webpack-dev-server": "webpack/webpack-dev-server#browser-log-level",

After npm install, go to cd node_modules/webpack-dev-server, and run npm run prepublish.

[gaearon]

These are useful errors and I want them to be reported. They are related to user’s code.

[gaearon]

Hey, thanks for taking a look!

So my problem is there’s no way to separate useful output (compilation warnings and errors) from useless output (generally anything prefixed with WDS—our users have no idea what WDS even is, and they don’t need 20 messages about being disconnected either).

My guess is there’s some bug causing repeated disconnects. It just isn’t right that it keeps retrying and spamming the console IMO.

[SpaceK33z]

@gaearon, I've updated the PR with your feedback.

• I no longer abuse quiet and noInfo. Instead, there is a separate option, clientLogLevel. You can set this to error, warning, info or none. It defaults to info.
  • Via the CLI you can use this with --client-log-level. Not sure about the name btw, so suggestions are welcome.
• Compilation errors will always be logged, disregarding the log level. Maybe there is a use-case where you don't want this, but we'll think about that when someone complains.
• The repeated message [WDS] Disconnected! will now only display once.
  • Unfortunately there doesn't seem to be a way to hide the ERR_CONNECTION_REFUSED errors. This is happening because the websocket tries to re-connect every two seconds.

[gaearon]

Thanks for taking the time to work on this.

This is happening because the websocket tries to re-connect every two seconds.

Is this useful? Can we make it reconnect three times and give up? Or reconnect with exponential backoff?

[SpaceK33z]

Is this useful? Can we make it reconnect three times and give up? Or reconnect with exponential backoff?

If your PC gets into sleep mode, and a tab with the dev-server is still open, the connection would not be restored when you get out of sleep mode. We should be able to do something smarter with it, so I've made #584 for this. It's a bit outside the scope of this PR.

Do you think the rest of this PR is good?

[gaearon]

Yep, thanks.

[gaearon]

The only issue is we’re still on 1.x and can’t jump to 2.x until it’s stable.
Any chance you’d be interested in backporting this to 1.x?

[farwayer]

@SpaceK33z It will be very nice if this option can control HMR output also.

[ibrahima]

If I understand correctly, as @farwayer said the HMR output is still logged regardless, so we're still getting some unhelpful spam (which, in my case, is annoying because our front end tests get spammed with it constantly). Not sure whether it's even possible for that code to use the same logger since it's in a different project, but here's the source: https://github.com/webpack/webpack/blob/master/hot/dev-server.js