npm run watch fails after update to webpack 2

[johneisenheim]

Hi there! Updating webpack to version 2.2.1, command npm run watch fails with the following result:

Waiting for dist/*.js (max 30 seconds)
[1] Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
[1]  - configuration has an unknown property 'debug'. These properties are valid:
[1]    object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, performance?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
[1]    The 'debug' property was removed in webpack 2.
[1]    Loaders should be updated to allow passing this option via loader options in module.rules.
[1]    Until loaders are updated one can use the LoaderOptionsPlugin to switch loaders into debug mode:
[1]    plugins: [
[1]      new webpack.LoaderOptionsPlugin({
[1]        debug: true
[1]      })
[1]    ]
[1]  - configuration.module has an unknown property 'postLoaders'. These properties are valid:
[1]    object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, loaders?, noParse?, rules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp? }
[1]    Options affecting the normal modules (`NormalModuleFactory`).
[1]  - configuration.resolve has an unknown property 'modulesDirectories'. These properties are valid:
[1]    object { alias?, aliasFields?, cachePredicate?, descriptionFiles?, enforceExtension?, enforceModuleExtension?, extensions?, fileSystem?, mainFields?, mainFiles?, moduleExtensions?, modules?, plugins?, resolver?, symlinks?, unsafeCache?, useSyncFileSystemCalls? }
[1]  - configuration.resolve.extensions[0] should not be empty.

Any solution?

Thanks!

[RickWong]

#141 (comment)