Error prompt:

Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.module has an unknown property 'loader'. These properties are valid:
   object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, loaders?, noParse?, rules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, unsafeCache?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp?, strictExportPresence?, strictThisContextOnImports?}
   -> Options affecting the normal modules (`NormalModuleFactory`).

Rules are used after webpack v2. Change the loaders in module to rules

Similar Posts:

• Cannot findmodule’webpack-cli/bin/config-yargs
• Invalid configuration object. Webpack has been initialised using a..
• [Solved] TypeError Error: Cannot read property ‘0’ of undefined
• [Solved] Module build failed: Error: Cannot find module ‘node-sass’
• [Solved] [email protected] Error: Cannot find module ‘webpack/bin/config-yargs‘
• The webpack handwritten loader introduces error: Module not found: Error: path argument is not a string
• Webpack high version pulls out CSS style and reports an error [Solved]
• Causes and solutions of error reporting in require setting dynamic path
• [Solved] Vue pdfjs-dist Error: Module parse failed: Unexpected token (2267:39)
• [Solved] Error: No module factory available for dependency type: ContextElementDependency