ng update and ng update --all do not agree with each other

[johnpapa]

Bug Report or Feature Request (mark with an x)

- [x ] bug report -> please search issues before submitting
- [ ] feature request

Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Versions

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

Repro steps

ng update
ng update --all

The log given by the failure

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.

Desired functionality

If ng update says it's all clear, then the ng update --all should agree. Not sure which is right.

Mention any other details that might be useful

[billfranklin]

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.

[brianivander]

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//issues/12243)]

How to fix this?

[sistr22]

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