Webpack v2.1.0-beta.23 breaks everything #2234

JohannesHoppe · 2016-09-19T23:50:54Z

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)

The text was updated successfully, but these errors were encountered:

valfran · 2016-09-20T00:32:10Z

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.

dudleycodes · 2016-09-20T00:44:17Z

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.

LaKing · 2016-09-20T00:45:33Z

Same here.

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

billdwhite · 2016-09-20T00:46:08Z

Same here.

Fix angular#2234

exequielc · 2016-09-20T00:57:09Z

same here!! please helps

josenriq · 2016-09-20T01:00:42Z

Same here:

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

ghost · 2016-09-20T01:00:58Z

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!

ghost · 2016-09-20T01:01:45Z

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

shusson · 2016-09-20T01:04:45Z

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

gbrits · 2016-09-20T01:15:42Z

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.

Fix #2234

ghost · 2016-09-20T01:38:57Z

Thanks @shusson, it's working fine now.

filipesilva · 2016-09-20T01:43:37Z

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.

angular/angular-cli#2234 (comment)

djwhatley · 2016-09-20T02:50:55Z

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)

jasonhodges · 2016-09-20T04:00:17Z

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

shusson · 2016-09-20T04:05:27Z

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

ghost · 2016-09-20T04:09:56Z

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.

hansl · 2016-09-20T04:10:21Z

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.

filipesilva · 2016-09-20T04:36:27Z

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

JohannesHoppe mentioned this issue Sep 19, 2016

chore(webpack): fixes webpack to 2.1.0-beta.22 to avoid broken CLI #2235

Closed

filipesilva added type: bug/fix P0 Issue that causes an outage, breakage, or major function to be unusable, with no known workarounds labels Sep 20, 2016

filipesilva added a commit to filipesilva/angular-cli that referenced this issue Sep 20, 2016

fix: pin beta package versions

b46e16b

Fix angular#2234

filipesilva mentioned this issue Sep 20, 2016

fix: pin beta package versions #2236

Merged

AndrewFeeney mentioned this issue Sep 20, 2016

Possible breaking changes introduced in Webpack 2.1.0-beta23 JeffreyWay/laravel-elixir-webpack-official#17

Closed

hansl closed this as completed in #2236 Sep 20, 2016

hansl pushed a commit that referenced this issue Sep 20, 2016

fix: pin beta package versions (#2236)

638a54b

Fix #2234

klaascuvelier added a commit to klaascuvelier/beautiful-places-to-run that referenced this issue Sep 20, 2016

update angular cli + fix webpack isue

5b42b68

angular/angular-cli#2234 (comment)

transtone mentioned this issue Sep 20, 2016

你好，项目运行异常 vuejs/vue-hackernews-2.0#29

Closed

angular locked and limited conversation to collaborators Sep 20, 2016

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Webpack v2.1.0-beta.23 breaks everything #2234

Webpack v2.1.0-beta.23 breaks everything #2234

JohannesHoppe commented Sep 19, 2016

Please provide us with the following information:

valfran commented Sep 20, 2016 •

edited

Loading

dudleycodes commented Sep 20, 2016 •

edited

Loading

LaKing commented Sep 20, 2016

billdwhite commented Sep 20, 2016

exequielc commented Sep 20, 2016

josenriq commented Sep 20, 2016

ghost commented Sep 20, 2016

ghost commented Sep 20, 2016

shusson commented Sep 20, 2016

gbrits commented Sep 20, 2016

ghost commented Sep 20, 2016

filipesilva commented Sep 20, 2016

djwhatley commented Sep 20, 2016 •

edited

Loading

jasonhodges commented Sep 20, 2016 •

edited

Loading

shusson commented Sep 20, 2016

ghost commented Sep 20, 2016

hansl commented Sep 20, 2016

filipesilva commented Sep 20, 2016

Webpack v2.1.0-beta.23 breaks everything #2234

Webpack v2.1.0-beta.23 breaks everything #2234

Comments

JohannesHoppe commented Sep 19, 2016

Please provide us with the following information:

valfran commented Sep 20, 2016 • edited Loading

dudleycodes commented Sep 20, 2016 • edited Loading

LaKing commented Sep 20, 2016

billdwhite commented Sep 20, 2016

exequielc commented Sep 20, 2016

josenriq commented Sep 20, 2016

ghost commented Sep 20, 2016

ghost commented Sep 20, 2016

shusson commented Sep 20, 2016

gbrits commented Sep 20, 2016

ghost commented Sep 20, 2016

filipesilva commented Sep 20, 2016

djwhatley commented Sep 20, 2016 • edited Loading

jasonhodges commented Sep 20, 2016 • edited Loading

shusson commented Sep 20, 2016

ghost commented Sep 20, 2016

hansl commented Sep 20, 2016

filipesilva commented Sep 20, 2016

valfran commented Sep 20, 2016 •

edited

Loading

dudleycodes commented Sep 20, 2016 •

edited

Loading

djwhatley commented Sep 20, 2016 •

edited

Loading

jasonhodges commented Sep 20, 2016 •

edited

Loading