-
Notifications
You must be signed in to change notification settings - Fork 12k
angular-cli: 1.0.0-beta.11-webpack.8: Uncaught TypeError: Cannot read property 'Emulated' of undefined in config.js:15
#2065
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The fix was reported to be using webpack beta.22. Guess there's your answer. |
According to official doc, I run |
For now you must. The fix for it is only available on master (yet to be released on |
So I tried this:
But, when I run ng serve, it eventually shows Webpack version as Absolutely clueless what to do. |
Finally got the
this will update webpack installation in angular-cli and angular-cli will stop picking beta 21 internally. Hence, closing the issue. |
Why is it insisting on installing beta.21?? The package.json file in the angular-cli folder specifies beta.22? Why should I have to fix their code? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Mac OSX (Yosemite)
ng --version
. If there's nothing outputted, please runin a Terminal:
node --version
and paste the result here:angular-cli: 1.0.0-beta.11-webpack.8
node: 6.1.0
os: darwin x64
do on your code? etc.
Router upgraded to rc.6
Followed this doc https://github.com/angular/angular-cli/blob/master/WEBPACK_UPDATE.md
to upgrade my current project to use angular-cli@webpack to run the app.
ng serve
Version: webpack 2.1.0-beta.21
webpack: bundle is now VALID.
Browser @ http://localhost:4200/ shows
Uncaught TypeError: Cannot read property 'Emulated' of undefined
inconfig.js:15
I did this upgrade last night so assuming it should pick the latest which was pushed to master 4 days back.
The text was updated successfully, but these errors were encountered: