-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Everything was working fine and suddenly these errors. #1019
Comments
@kodeine looks like something broke with |
@scottopherson yeah i downgraded to beta22 as well and it works. |
I had same issue, this fixed it
|
I'm having this exact same error with tslint but it's form a vanilla downloaded angular2-webpack-starter with beta21 |
Same issue: node -v : 6.6.0 I get this same issue not locally but on codeship and heroku deploy process. No major changes besides the node version bump from 6.5 to 6.6 and added a few components, any ideas on how to fix. I use a angular webpack starter version that uses "webpack": "^2.1.0-beta.21" |
@lgarro You'll likely encounter the issue locally if you run |
That worked @matthewsorenson-tr thanks |
Is there any fix for this issue with 2.1.0-beta.23 instead of downgrading it to 2.1.0-beta.22? |
2.1.0-beta.24 is available ;) |
@gaurav2887 Update the webpack.*.js files to match the new format. There is a migration example at the end of the beta.23 release notes that may help with that: https://github.com/webpack/webpack/releases |
Using one of the new configuration option specified in the schema also solves the problem. For instance modulesDirectories has changed to simply modules in the later betas. Webpack issue #3018 has an interesting discussion around whether this should have been made a breaking change. |
hello,
everything was working fine and suddenly i cant start the hmr server.
Any idea's?
UPDATE
so it seems like i changed
"^webpack": "2.1.0-beta.21"
to"webpack": "2.1.0-beta.21",
and it works, looks like webpack": "2.1.0-beta.23 does not work with material2 branch.OLD
The text was updated successfully, but these errors were encountered: