Invalid configuration object

[ghost]

Win10, Already have NG2, Angular CLI installed globally. Pulled the most tonight & ran npm install & ng serve - got back a series of errors: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

• configuration has an unknown property 'tslint'. These properties are valid: object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, 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: { tslint: ... } }) }
  • configuration.module has an unknown property 'preLoaders'. These properties are valid: object { exprContextCritical?, exprContextRecursive?, exprContextRegExp?, exprContextRequest?, loaders?, noParse?, rules?, unknownContextCritical?, unknownContextRecursive?, unknownContextRegExp?, unknownContextRequest?, wrappedContextCritical?, wrappedContextRecursive?, wrappedContextRegExp? } Options affecting the normal modules (NormalModuleFactory).
• configuration.node.global should be a boolean.
• configuration.resolve has an unknown property 'root'. These properties are valid: object { alias?, aliasFields?, cachePredicate?, descriptionFiles?, enforceExtension?, enforceModuleExtension?, extensions?, fileSystem?, mainFields?, mainFiles?, moduleExtensions?, modules?, plugins?, resolver?, symlinks?, unsafeCache? }
• configuration.resolve.extensions[0] should not be empty.

[adrianwilson]

This seems to be an issue with a new version of webpack, forcing the angular cli team to lock down an older version https://github.com/angular/angular-cli/issues/2234 Confirmed Installing angular-cli@1.0.0-beta.15 locally solves this issue.

npm i angular-cli@1.0.0-beta.15 -D