-
Notifications
You must be signed in to change notification settings - Fork 12k
Cannot find module 'webpack' after moving from @latest to @next #11148
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
I think that was some badly configured peer dependencies on our side. #11152 should fix it. |
Getting you the latest TypeScript was fixed by angular/devkit#987 |
I think everything here is now fixed. |
Try this... npm uninstall --save webpack |
don't try it, we don't have to install webpack it will break if you will execute rm -rf node_modules |
I had to delete package-lock.json, then remove and reinstall node_modules. |
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. |
Bug Report or Feature Request (mark with an
x
)Area
Versions
Repro steps
I was in cli 6 and want try
ng update --next --all
it cancel me cause of peer dependancesng update --next --all --force
success but get me last version of typescrip, I need manually in package.json write ~2.7.2 thennpm install
After that I run
ng serve
and I get :Then I remove
node_modules
manually then rerunnpm install
-> same error output.Desired functionality
First of all avoid always update typescript to last version keep only supported version. Then I desire to update easily.
Mention any other details that might be useful
Actually I can't quit this @next and come back to @latest I need fix my package.json manually. Damn!
cc @filipesilva
The text was updated successfully, but these errors were encountered: