Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

?- configuration has an unknown property 'devSever'. These properties are valid:

? ?object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, parallelism?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }

? ?For typos: please correct them.

? ?For loader options: webpack 2 no longer allows custom properties in configuration.

? ? ?Loaders should be updated to allow passing options via loader options in module.rules.

? ? ?Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:

? ? ?plugins: [

? ? ? ?new webpack.LoaderOptionsPlugin({

? ? ? ? ?// test: /\.xxx$/, // may apply this only for some modules

? ? ? ? ?options: {

? ? ? ? ? ?devSever: ...

? ? ? ? ?}

? ? ? ?})

? ? ?]

npm ERR! code ELIFECYCLE

npm ERR! errno 1

npm ERR! 01.webpack-study@1.0.0 dev2: `cross-env NODE_ENV=development webpack-dev-server --config webpack.config.js`

npm ERR! Exit status 1

npm ERR!

npm ERR! Failed at the 01.webpack-study@1.0.0 dev2 script.

npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

npm ERR!? ? ?C:\Users\Administrator\AppData\Roaming\npm-cache\_logs\2018-08-19T08_33_01_555Z-debug.log