question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

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

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:4
  • Comments:6

github_iconTop GitHub Comments

2reactions
sistr22commented, Sep 23, 2018

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

0reactions
angular-automatic-lock-bot[bot]commented, Oct 30, 2020

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Don't be afraid and just `ng update`! | by beeman | ITNEXT
In this article we take a look at the Angular release process, and why we all benefit from a predictable release cycle.
Read more >
ng update - Angular
Perform a basic update to the current stable release of the core framework and CLI by running the following command. content_copy ng update...
Read more >
angular - ng update to specific version - Stack Overflow
I end up with errors like Package "ng-chartjs" has an incompatible peer dependency to "@angular/common" (requires "*", would install "9.0.0-next ...
Read more >
How To Update Angular CLI To Latest Version
To update Angular CLI to latest version Angular, use ng update @angular/core @angular/cli@latest command.
Read more >
Angular Version Upgrade: A quick guide to upgrade from 9.0 ...
Sometimes the version upgrades are missed due to other high-priority commitments and ... ng update @angular/core@10 @angular/cli@10 --force.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found