Webpack v2.1.0-beta.23 breaks everything

Question

Webpack v2.1.0-beta.23 breaks everything

JohannesHoppe opened this issue 8 years ago · comments

In short, please pin the webpack version to v2.1.0-beta.22.
beta 23 has breaking changes: https://github.com/webpack/webpack/releases/tag/v2.1.0-beta.23
PR follows soon!

....

Please provide us with the following information:

OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)
Windows
Versions. Please run ng --version. If there's nothing outputted, please run
in a Terminal: node --version and paste the result here:
angular-cli: 1.0.0-beta.14
Repro steps. Was this an app that wasn't created using the CLI? What change did you
do on your code? etc.
ng new foo-bar
npm start
The log given by the failure. Normally this include a stack trace and some
more information.

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?, devServer?, devtool?, entry, externals?, loader?, module?, name?, dependencies?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
 - configuration.module has an unknown property 'preLoaders'. These properties are valid:
   object { rules?, loaders?, noParse?, unknownContextRequest?, unknownContextRegExp?, unknownContextRecursive?, unknownContextCritical?, exprContextRequest?, exprContextRegExp?, exprContextRecursive?, exprContextCritical?, wrappedContextRegExp?, wrappedContextRecursive?, wrappedContextCritical? }
   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 { modules?, descriptionFiles?, plugins?, mainFields?, aliasFields?, mainFiles?, extensions?, enforceExtension?, moduleExtensions?, enforceModuleExtension?, alias?, symlinks?, unsafeCache?, cachePredicate?, fileSystem?, resolver? }
 - configuration.resolve.extensions[0] should not be empty.
WebpackOptionsValidationError: 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?, devServer?, devtool?, entry, externals?, loader?, module?, name?, dependencies?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
 - configuration.module has an unknown property 'preLoaders'. These properties are valid:
   object { rules?, loaders?, noParse?, unknownContextRequest?, unknownContextRegExp?, unknownContextRecursive?, unknownContextCritical?, exprContextRequest?, exprContextRegExp?, exprContextRecursive?, exprContextCritical?, wrappedContextRegExp?, wrappedContextRecursive?, wrappedContextCritical? }
   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 { modules?, descriptionFiles?, plugins?, mainFields?, aliasFields?, mainFiles?, extensions?, enforceExtension?, moduleExtensions?, enforceModuleExtension?, alias?, symlinks?, unsafeCache?, cachePredicate?, fileSystem?, resolver? }
 - configuration.resolve.extensions[0] should not be empty.
    at webpack (E:\Angular2Buch\angular2-workshop-devmedia\node_modules\webpack\lib\webpack.js:16:9)
    at Class.run (E:\Angular2Buch\angular2-workshop-devmedia\node_modules\angular-cli\tasks\serve-webpack.js:23:27)
    at E:\Angular2Buch\angular2-workshop-devmedia\node_modules\angular-cli\commands\serve.js:84:26
    at process._tickCallback (internal/process/next_tick.js:103:7)

valfran · Answer 1 · Tue Sep 20 2016 08:32:10 GMT+0800 (China Standard Time)

Same problem here, creating an angular Project using ng new first-app, then trying to run with ng serve (no changes were made on the generated project):
OS: Windows 10
Version:
angular-cli: 1.0.0-beta.14
node: 6.6.0
os: win32 x64

Steps:
ng new first-app
cd first-app
ng serve

LOG:
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?, devServer?, devtool?, entry, externals?, loader?, module?, name?, dependencies?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
configuration.module has an unknown property 'preLoaders'. These properties are valid:
object { rules?, loaders?, noParse?, unknownContextRequest?, unknownContextRegExp?, unknownContextRecursive?, unknownContextCritical?, exprContextRequest?, exprContextRegExp?, exprContextRecursive?, exprContextCritical?, wrappedContextRegExp?, wrappedContextRecursive?, wrappedContextCritical? }
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 { modules?, descriptionFiles?, plugins?, mainFields?, aliasFields?, mainFiles?, extensions?, enforceExtension?, moduleExtensions?, enforceModuleExtension?, alias?, symlinks?, unsafeCache?, cachePredicate?, fileSystem?, resolver? }
configuration.resolve.extensions[0] should not be empty.

James Dudley · Answer 2 · Tue Sep 20 2016 08:44:17 GMT+0800 (China Standard Time)

Same problem. Was trying to figure out why an existing project broke; created new using ng new test-app. ng build fails

OS: Windows 10 x64
angular-cli: 1.0.0-beta.14
node: 6.5.0

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?, devServer?, devtool?, entry, externals?, loader?, module?, name?, dependencies?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?
, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
 - configuration.module has an unknown property 'preLoaders'. These properties are valid:
   object { rules?, loaders?, noParse?, unknownContextRequest?, unknownContextRegExp?, unknownContextRecursive?, unknownContextCritical?, exprContextRequest?, exprContextRegExp?, exprContextRecursive?, exprConte
xtCritical?, wrappedContextRegExp?, wrappedContextRecursive?, wrappedContextCritical? }
   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 { modules?, descriptionFiles?, plugins?, mainFields?, aliasFields?, mainFiles?, extensions?, enforceExtension?, moduleExtensions?, enforceModuleExtension?, alias?, symlinks?, unsafeCache?, cachePredica
te?, fileSystem?, resolver? }
 - configuration.resolve.extensions[0] should not be empty.

István Király · Answer 3 · Tue Sep 20 2016 08:45:33 GMT+0800 (China Standard Time)

Same here.

Fedora 14
angular-cli: 1.0.0-beta.14
node: 5.9.1
os: linux x64

Bill White · Answer 4 · Tue Sep 20 2016 08:46:08 GMT+0800 (China Standard Time)

Same here.

Exequiel Catalani · Answer 5 · Tue Sep 20 2016 08:57:09 GMT+0800 (China Standard Time)

same here!! please helps

Jose E. Bolaños · Answer 6 · Tue Sep 20 2016 09:00:42 GMT+0800 (China Standard Time)

Same here:

Mac OSX
angular-cli: 1.0.0-beta.14
node: 5.10.0
os: darwin x64

Deleted user · Answer 7 · Tue Sep 20 2016 09:00:58 GMT+0800 (China Standard Time)

Yup, sorry to add to the noise but I'm getting the exact same error message on
angular-cli: 1.0.0-beta.14
node: 6.2.2
os: darwin x64
Sadly, I discovered this after I had gone through the tedious process of installing material components, angularfire, etc... Hope I don't have to ng new another app and start all over!

Deleted user · Answer 8 · Tue Sep 20 2016 09:01:45 GMT+0800 (China Standard Time)

I know the issue was only filed an hour ago but I hope someone stops by to help soon!

Shane Husson · Answer 9 · Tue Sep 20 2016 09:04:45 GMT+0800 (China Standard Time)

@colindevs as a work around you can fix webpack to v2.1.0-beta.22 in your apps package.json

Grant Brits · Answer 10 · Tue Sep 20 2016 09:15:42 GMT+0800 (China Standard Time)

Thanks @colindevs - anyone using Laravel (laravel-elixir-webpack-official) just do:

npm uninstall webpack --save-dev

followed by

npm install webpack@2.1.0-beta.22 --save-dev

Then you should be able to gulp again. Fixed the issue for me.

Deleted user · Answer 11 · Tue Sep 20 2016 09:38:57 GMT+0800 (China Standard Time)

Thanks @shusson, it's working fine now.

Filipe Silva · Answer 12 · Tue Sep 20 2016 09:43:37 GMT+0800 (China Standard Time)

We'll have a release in the next day or so that fixes this issue. Until then, please see #2234 (comment) for a temporary fix.

Daniel Whatley · Answer 13 · Tue Sep 20 2016 10:50:55 GMT+0800 (China Standard Time)

I'm still having the issue even after the workaround.

angular-cli: 1.0.0-beta.14
node: 6.5.0
os: win32 x64 (Windows 10.0.10586)

Jason Hodges · Answer 14 · Tue Sep 20 2016 12:00:17 GMT+0800 (China Standard Time)

I've been following the latest developments here yet I still have not had success getting a clean install to serve a project.

uninstall angular-cli
cleaned cache
reinstalled angular-cli
ng new
cd
ng serve
and..
Still receiving the Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema. dump.
These steps have been performed after the PR was merged in to pin the beta dependencies.

angular-cli: 1.0.0-beta.14
node: 4.4.5
os: darwin x64

Shane Husson · Answer 15 · Tue Sep 20 2016 12:05:27 GMT+0800 (China Standard Time)

@jasonhodges you need to fix the webpack version in your app to v2.1.0-beta.22.

Deleted user · Answer 16 · Tue Sep 20 2016 12:09:56 GMT+0800 (China Standard Time)

To reiterate @shusson's fix which is up a bit: tweak your package.json

npm uninstall webpack --save-dev
npm install webpack@2.1.0-beta.22 --save-dev

ng build or ng serve will then work.

Hans Larsen · Answer 17 · Tue Sep 20 2016 12:10:21 GMT+0800 (China Standard Time)

Thank you for reporting. This issue has been fixed and we're now working to get an updated beta to you right away.

Per the code of conduct for Angular, I’ve deleted a couple of comments that veered into trolling, and have locked this issue. Please keep issues and comments technical and constructive. We are working hard to deliver a large project of which webpack-CLI is one part; often we can’t act instantly to resolve an issue. We’re sorry for this regression and are working to resolve.

Filipe Silva · Answer 18 · Tue Sep 20 2016 12:36:27 GMT+0800 (China Standard Time)

1.0.0-beta.15 is out now which fixes this issue.