You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
webpack and webpack-dev-server version:
webpack: 2.1.0-beta.26
webpack-dev-server: 2.1.0-beta.11
Please tell us about your environment:
OSX 10.11.6
Running server Node.js API
Current behavior:
Silent fail when providing an option to the devServer config that's outside of the schema.
Expected/desired behavior:
One of two:
a) handle the extraneous config option "gracefully" by either clearing the invalid option from the config or simply ignoring it if no harm could come by having it there
b) simply throw an error because an invalid option has been provided
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem along with a gist/jsbin of your Webpack configuration. Be sure to specify how you are running the server.
I brought this up on #654 where my config looked like:
In this example, colors is the extraneous config option and that will freeze the Webpack execution altogether. To clarify, this will happen regardless of what the extraneous config, and no error or log item is thrown; just radio silence. However, it's worth noting that there's an object returned from new webpackDevServer but listen doesn't seem to execute.
The text was updated successfully, but these errors were encountered:
I tried to reproduce it with this example. In server.js, I added colors: true in the second parameter for new WebpackDevServer. This resulted in a proper error, as expected.
Could you share how you start the Node.js server? I noticed you're using devServer from your config. Note that the Node.js API will ignore the options in devServer, unless you specifically add it (e.g. new WebpackDevServer(compiler, config.devServer)).
I'm submitting a bug report
webpack and webpack-dev-server version:
webpack: 2.1.0-beta.26
webpack-dev-server: 2.1.0-beta.11
Please tell us about your environment:
OSX 10.11.6
Running server Node.js API
Current behavior:
Silent fail when providing an option to the
devServer
config that's outside of the schema.Expected/desired behavior:
One of two:
a) handle the extraneous config option "gracefully" by either clearing the invalid option from the config or simply ignoring it if no harm could come by having it there
b) simply throw an error because an invalid option has been provided
I brought this up on #654 where my config looked like:
In this example,
colors
is the extraneous config option and that will freeze the Webpack execution altogether. To clarify, this will happen regardless of what the extraneous config, and no error or log item is thrown; just radio silence. However, it's worth noting that there's an object returned fromnew webpackDevServer
butlisten
doesn't seem to execute.The text was updated successfully, but these errors were encountered: