ng upgrade: incompatible peer dependency error prevents from auto-updating

[juristr]

Versions

Angular CLI: 6.0.1
Node: 9.11.1
OS: darwin x64
Angular: 5.2.10
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.1
@angular-devkit/build-angular     0.6.1
@angular-devkit/build-optimizer   0.6.1
@angular-devkit/core              0.6.1
@angular-devkit/schematics        0.6.1
@angular/cli                      6.0.1
@ngtools/webpack                  6.0.1
@schematics/angular               0.6.1
@schematics/update                0.6.1
rxjs                              5.5.10
typescript                        2.5.3
webpack                           4.6.0


macOS 10.11.6

Repro steps

• Clone the upgrade branch of repo https://github.com/juristr/ng-upgrade-test
• yarn install (or npm install => I used yarn)
• Try upgrading the Angular dependencies, using for instance ng update @angular/core. I already performed the @angular/cli upgrade command which adjusts the angular.json etc.

Observed behavior

<!-- Normally this includes a stack trace and some more information. -->

I get the following output

❯ ng update @angular/core
                  Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=2.7.2 <2.8", would install "2.5.3")
Incompatible peer dependencies found. See above.

Desired behavior

It should automatically update the Angular dependencies as well as RxJS and TypeScript (as described in the update.angular.io guide).

Mention any other details that might be useful (optional)

[juristr]

@clydin Hi, I was chatting about this in the Angular Slack with @filipesilva and he told me to open the issue here. Let me know if you need more info. Thanks a lot 👍

[brandonroberts]

I'm running into a similar issue when trying to update NgRx.

If I have all the @ngrx libraries installed and I run ng update @ngrx/store --next I get

Package "@ngrx/schematics" has a missing peer dependency of "@angular-devkit/core" @ "^0.6.0".

If I run yarn list @angular-devkit/core, I see

@angular-devkit/core@0.6.1

[intellix]

Not sure if it's the same thing, but I'm getting errors like:

Package "bootstrap" has a missing peer dependency of "jquery" @ "1.9.1 - 3".

I'm using the bootstrap SCSS framework but have no intentions of ever including jQuery ofc. I dunno if this is a problem with bootstrap itself that it has jquery as a peerDep or if the problem is that CLI throws for peer dep WARN.

Is it perhaps possible to just force the ng update --all?

[Teamop]

I have the same issue, but instead run ng update @angular/compiler-cli successfully without error.

[getabetterpic]

I'm running into this issue as well, seems the updater is trying to install typescript@2.8.3 but @angular/compiler-cli has a peer dependency of typescript@">=2.7.2 <2.8".

[sachinpachori]

When I ran "ng update @angular/core" got the following errors and cannot upgrade to angular 6:
Package "angular2-resizable" has an incompatible peer dependency to "@angular/core" (requires ">=3.0.0-rc.0 <4.0.0||>=2.0.0 <3.0.0", would install "6.0.2").
Package "codelyzer" has an incompatible peer dependency to "@angular/compiler" (requires ">=5.0.0-rc.0 <6.0.0||>=2.3.1 <3.0.0||>=4.0.0-beta <5.0.0", would install "6.0.2").

[brandonroberts]

Just so its noted, the workaround is to use the --force flag when running ng update [package] to override the dependency issues. This will upgrade the packages anyway and you can verify your app with the updated dependencies. If that third party dependency still needs to be updated because of breaking changes, then that package will need to be updated.

ng update @ngrx/store --next --force

[clydin]

@sachinpachori Those are actually legitimate errors. The project has a dependency (angular2-resizable) that does not support Angular 6. As @brandonroberts mentions, the --force flag can be used (with caution) to update while ignoring those issues.
And similar with codelyzer; however, since codelyzer is part of the default project this could potentially (and in the future) be automatically updated (depending on the pinning strategy) with a CLI update.

[sachinpachori]

@brandonroberts @clydin thank you that solved my issue.