clientLogLevel 'none' is invalid 2.1.0-beta.11

[stevewillard]

Version:
webpack-dev-server: 2.1.0-beta.11

In my webpack config I have:

  devServer : {
    clientLogLevel: 'none'
  },

With the latest webpack-dev-server I get this:

Invalid configuration object. webpack-dev-server has been initialised using a configuration object that does not match the API schema.
 - configuration.clientLogLevel should be one of these:
   "info" | "warning" | "error"
   Controls the log messages shown in the browser.

is 'none' a valid configuration?

[SpaceK33z]

Whoops, fixed. I'll wait a few days before releasing a new version to see if there are more issues with the new schema validation.

Thanks for your bug report!

[josh18]

I also was having this issue until I found what it was via trial and error. But this is the error message I was getting:

.../node_modules/webpack-dev-server/lib/Server.js:25
throw new OptionsValidationError(validationErrors);
^

Any idea what I am doing different?
node v7.1.0 npm v3.10.8

[stevewillard]

You just have to downgrade WDS and wait until the next version is released.

[josh18]

I'm just trying to figure out why you got an actual error message but I just got throw new OptionsValidationError(validationErrors);? It looks like it failed on "throw"? Might have nothing to do with WDS though so I'll do some research and see what I can find.

[SpaceK33z]

Fix released in v2.1.0-beta.12.

[josh18]

By the way the error doesn't get thrown properly in Node v7 for some reason (it might well be Nodes fault). It only shows the stack trace and not the message. It works fine on Node v6 or if you put this line at the bottom of the function.

[SpaceK33z]

Yeah there are many issues with Node.js v7. A few minutes ago I put a warning on the README, because the Node.js v7 issues seem endless and are not the fault of webpack-dev-server most of the time.

[josh18]

Ah ok, good to know.