x)- [x ] bug report -> please search issues before submitting
- [ ] feature request
x)- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc
Angular CLI: 6.1.2
Node: 8.11.4
OS: darwin x64
Angular:
...
Package Version
------------------------------------------------------
@angular-devkit/architect 0.7.2
@angular-devkit/core 0.7.2
@angular-devkit/schematics 0.7.2
@schematics/angular 0.7.2
@schematics/update 0.7.2
rxjs 6.2.2
typescript 2.7.2
ng update
ng update --all
ng update
We analyzed your package.json and everything seems to be in order. Good work!
~/_git/vikings master ✗ 17h22m ⚑
â–¶ng update --all
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.10", would install "3.0.3").
Incompatible peer dependencies found. See above.
If ng update says it's all clear, then the ng update --all should agree. Not sure which is right.
also getting 'unable to verify the first certificate' for packages like primeng that work fine in NPM but fail on 'ng update primeng'. Something bad has happened to ng update.
I have the same problem:
Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.10", would install "3.0.3")
This might be the same issue: [(https://github.com/angular/angular-cli/issues/12243)]
How to fix this?
instead of doing the ng update --all I.m running each update one by one:
ng update @angular/core
[...]
It seems to be working so far ... weird
@Whiteseeker, I'm doing the same, but ng update is literally taking 20-30+min on each manual update. I found another issue that is closed and that issue essentially concluded: ng update is terrible in terms of performance and user experience, deal with it.
Are you having the same experience? It has taken me nearly the entire workday to update my project.
Any updates to this old issue? :)
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
instead of doing the ng update --all I.m running each update one by one:
ng update @angular/core
[...]
It seems to be working so far ... weird