Incorrect peer dependency when upgrading Angular material
See original GitHub issueI am migrating my angular application to 8, and as part of the process I’m updating Angular Material.
ng update @angular/material
This causes the following error:
Package "@ngx-translate/http-loader" has an incompatible peer dependency to "@angular/common" (requires ">=7.0.0", would install "9.0.0-next.5").
Package "@ngx-translate/core" has an incompatible peer dependency to "@angular/core" (requires ">=7.0.0", would install "9.0.0-next.5").
Any idea what the issue is?
Issue Analytics
- State:
- Created 4 years ago
- Comments:10
Top Results From Across the Web
Yarn: "Incorrect peer dependency" Me - angular - Stack Overflow
The angular5-csv library has not been update for 7 months (npmjs), if you want to get rid of the warnings you should remove...
Read more >incorrect peer dependency and has unmet peer dependency ...
We are concerned about the incorrect peer dependency and has unmet peer dependency warnings: C:\Users\Foo\source\repos\CompassZero\angular>yarn ...
Read more >Upgrading Angular versions has to be the most frustrating ...
First problem: Package "@angular-eslint/schematics" has an incompatible peer dependency to "@angular/cli" (requires ">= 12.0.0 ...
Read more >Unable to resolve dependency tree error in Angular while ...
It's a dependency conflict (incorrect and potentially broken dependency) error, so run the command with --force or --legacy-peer-deps flag.
Read more >conflicting peer dependency: jasmine-core@4.4.0 - You.com
You are using npm 7.x, which is more strict about peer dependencies than npm 6.x. The easiest solution is to run npm install...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
ok, thanks for the help. I am not trying to install 9 anywhere, nor using @next, the only command I’m running to get this error is using angular’s cli
ng
to update material. Maybe there’s a bug in the latest cli for that command. seems unlikely. I will post if I find outIt’s a bug in angular cli: https://stackoverflow.com/questions/57297479/got-angular-version-9-0-0-next-0-when-tried-to-upgrade-to-angular-material-8