Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.1.1 <3.3", would install "3.4.5"). #14561

jtsom · 2019-05-29T12:02:02Z

🐞 Bug report

Command (mark with an `x`)

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

Is this a regression?

Yes

Yes, the previous version in which this bug was not present was: ....

Description

Having this issue trying to do an ng update on a pretty stock angular 7 application to angular 8:

ng update @angular/cli
Your global Angular CLI version (8.0.0) is greater than your local
version (7.3.8). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
                  Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.1.1 <3.3", would install "3.4.5").
Incompatible peer dependencies found. See above.

package.json:

{
  "name": "sample-player",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/animations": "~7.2.0",
    "@angular/common": "~7.2.0",
    "@angular/compiler": "~7.2.0",
    "@angular/core": "~7.2.0",
    "@angular/forms": "~7.2.0",
    "@angular/platform-browser": "~7.2.0",
    "@angular/platform-browser-dynamic": "~7.2.0",
    "@angular/router": "~7.2.0",
    "core-js": "^2.5.4",
    "rxjs": "~6.3.3",
    "tslib": "^1.9.0",
    "videogular2": "^6.4.0",
    "zone.js": "~0.8.26"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.13.0",
    "@angular/cli": "~7.3.8",
    "@angular/compiler-cli": "~7.2.0",
    "@angular/language-service": "~7.2.0",
    "@types/node": "~8.9.4",
    "@types/jasmine": "~2.8.8",
    "@types/jasminewd2": "~2.0.3",
    "codelyzer": "~4.5.0",
    "jasmine-core": "~2.99.1",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~4.0.0",
    "karma-chrome-launcher": "~2.2.0",
    "karma-coverage-istanbul-reporter": "~2.0.1",
    "karma-jasmine": "~1.1.2",
    "karma-jasmine-html-reporter": "^0.2.2",
    "protractor": "~5.4.0",
    "ts-node": "~7.0.0",
    "tslint": "~5.11.0",
    "typescript": "~3.2.2"
  }
}

🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

The text was updated successfully, but these errors were encountered:

jtsom · 2019-05-29T12:17:30Z

Also, do we have to do a git commit after every update operation??

ng update @angular/core
Repository is not clean.  Please commit or stash any changes before updating.

alan-agius4 · 2019-05-29T12:30:10Z

Also related to #13095

@jtsom, you can run multiple migrations as such: ng update @angular/cli @angular/core

jtsom · 2019-05-29T12:32:21Z

I did see #13095 but wanted to specifically target the new 8.0 (where it says it supports Typescript 3.4 - except where it doesn't....)

jtsom · 2019-05-29T12:52:08Z

I was able to get the update to run using the --force flag, but it looks like the operations that are run after the update (updating tsconfig.json, tslint.json, etc) were not run. How do I re-run those schematics to get everything up to date?

alan-agius4 · 2019-05-29T13:01:18Z

You can run ng update @angular/cli--from 7 --to 8 --migrate-only

jtsom · 2019-05-29T13:44:44Z

Except:

ng update @angular/cli --from 7 --to 8 --migrate-only
Using package manager: 'npm'
Collecting installed dependencies...
Found 32 dependencies.
Invalid Version: 7

alan-agius4 · 2019-05-29T15:30:34Z

@jtsom, yeah there is another issue with command, kindly see #14559 (comment)

marc-wilson · 2019-05-29T21:39:32Z

Ran into this as well. The only way I could get angular to upgrade 8 (from 7) was to use npm install @angular/[email protected] --save-dev (opposed to ng update @angular/cli

once I did this, I ran into the issue @jtsom called out:

Repository is not clean. Please commit or stash any changes before updating.

Once I committed the changes and ran ng update --all, I get more warnings:

Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.4 <3.5", would install "3.5.1")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=3.1 < 3.5", would install "3.5.1")
                  Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.4 <3.5", would install "3.5.1").
Incompatible peer dependencies found. See above.

tc9011 · 2019-05-30T03:27:52Z

@mswilson4040 same problem, Finally I use npm to update angular, like this:

npm install @angular/cli@latest @angular-devkit/build-angular@latest  --save-dev

npm install @angular/{common,compiler,compiler-cli,core,forms,platform-browser,platform-browser-dynamic,platform-server,router,animations}@latest [email protected] --save

After update, you should manually add parameter to ViewChild or ContentChild

alan-agius4 · 2019-05-30T05:45:07Z

Hi, are you running ng update @angular/cli @angular/core? You need to update both the CLI and the framework at the same time.

tc9011 · 2019-05-30T05:53:21Z

@alan-agius4 yes, I run ng update @angular/cli at first, and it worked well, but after I run ng update @angular/core , it said Repository is not clean. Please commit or stash any changes before updating

kswarthout · 2019-05-30T08:55:48Z

I encountered the same issues. The warning is related to your git repo. Committing my recent changes fixed the problem, and I was able to run the ng update commands (i.e. ng update @angular/cli @angular/core)

TomySmit · 2019-05-30T12:31:44Z

run this command git status --porcelain and add files and directories to ignore file or commit

RogierdeRuijter · 2019-05-30T16:17:08Z

run this command git status --porcelain and add files and directories to ignore file or commit

Fixing my git ignore worked for me.

huyinghuan · 2019-05-31T02:24:00Z

npm install -g @angluar/cli
ng update --all --force
ng add @angular/http

it work fine for ng server and ng build

damingerdai · 2019-05-31T02:34:24Z

i also meet this error.
first,i run

ng update @angular/core

and them

ng update @angular/cli

i don't run

ng update rxjs

now i have upgraded to angular8 and every thing sees ok.
i hope it is helpful

KylerJohnson26 · 2019-05-31T17:33:07Z

I had the same errors. Here's what worked for me:

I ran the following to update the global version of the Angular CLI:
npm i -g @angular/[email protected]

Then I ran the following to update my angular project:
ng update --all --force

Note: It's important to have a clean, up-to-date repo before running trying to update

tc9011 · 2019-06-01T03:19:34Z

run this command git status --porcelain and add files and directories to ignore file or commit

Before you use ng update, you should commit or stash all files

Laurens-makel · 2019-06-01T09:54:44Z

i also meet this error.
first,i run
ng update @angular/core
and them
ng update @angular/cil
i don't run
ng update rxjs
now i have upgraded to angular8 and every thing sees ok.
i hope it is helpful

Thanks, seems to be working!
Btw, you made a little spelling mistake in your ng update @angular/cil command, it should be ng update @angular/cli

matheo · 2019-06-01T20:30:21Z

On a side note, I had to run ng update @angular/material --from 7 --to 8 --migrate-only multiple times, committing the changes and trying again, because it was throwing FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory after editing my import paths on tons of components.

Thanks for the great work tho!

damingerdai · 2019-06-02T13:48:29Z

i also meet this error.
first,i run
ng update @angular/core
and them
ng update @angular/cil
i don't run
ng update rxjs
now i have upgraded to angular8 and every thing sees ok.
i hope it is helpful
Thanks, seems to be working!
Btw, you made a little spelling mistake in your ng update @angular/cil command, it should be ng update @angular/cli

Thanks

jtsom · 2019-06-02T15:17:24Z

Just tried to update another project and got:

ng update @angular/cli @angular/core @angular/cdk @angular/material
Your global Angular CLI version (8.0.1) is greater than your local
version (7.1.4). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
    packageGroup metadata of package @angular/cli is malformed. Ignoring.
    packageGroup metadata of package @angular/cli is malformed.
    packageGroup metadata of package @angular/cli is malformed. Ignoring.
    packageGroup metadata of package @angular/cli is malformed. Ignoring.
    packageGroup metadata of package @angular/cli is malformed.
    packageGroup metadata of package @angular/cli is malformed. Ignoring.
    packageGroup metadata of package @angular/cli is malformed. Ignoring.
    packageGroup metadata of package @angular/cli is malformed.
    packageGroup metadata of package @angular/cli is malformed. Ignoring.
    packageGroup metadata of package @angular/cli is malformed. Ignoring.
                  Package "@ncstate/sat-popover" has an incompatible peer dependency to "@angular/cdk" (requires "^7.0.0", would install "8.0.0").
Incompatible peer dependencies found. See above.

getting worse...

fr0 · 2019-06-04T19:06:10Z

What's the solution for this? Running ng update --all gives a bunch of errors.

                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=3.1 < 3.5", would install "3.5.1")
                  Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.4 <3.5", would install "3.5.1")
                  Package "ng-packagr" has an incompatible peer dependency to "typescript" (requires ">=2.7 < 3.5", would install "3.5.1")
                  Package "@angular-devkit/build-angular" has an incompatible peer dependency to "typescript" (requires ">=3.1 < 3.5", would install "3.5.1").
Incompatible peer dependencies found. See above.

marc-wilson · 2019-06-04T19:46:24Z

I've never actually seen ng update --all work. I was able to get things working by doing ng update @angular/core @angular/cli

fr0 · 2019-06-04T19:49:46Z

If ng update --all doesn't work, then it should be removed.

Or at the very least, this message should be changed:

 We analyzed your package.json, there are some packages to update:
    
      Name                               Version                  Command to update
     --------------------------------------------------------------------------------
      @angular/cli                       7.3.9 -> 8.0.1           ng update @angular/cli
      @angular/core                      7.2.15 -> 8.0.0          ng update @angular/core
    
    
    There might be additional packages that are outdated.
    Run "ng update --all" to try to update all at the same time.

marc-wilson · 2019-06-04T19:52:13Z

Yea, it's immediately suspicious when it reads Run "ng update --all" to _try_ to update all at the same time.

astronaute77 · 2019-06-09T15:08:19Z

Also having the same issue when running ng update --all:

Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.4 <3.5", would install "3.5.1").

Random90 · 2019-06-10T19:00:08Z

Same here, ng update --all throws typescript dependency error, but ng update @angular/core @angular/cli worked.

kishore0207 · 2019-06-11T08:50:09Z

Am updating the angular 7 to 8, after updating the ng update @angular/cli @angular/core command updated successfully,
but after updating the material through ng update @angular/material entered, then i got the error.
Repository is not clean. Please commit or stash any changes before updating.

deeja · 2019-06-11T22:50:38Z

Repository is not clean. Please commit or stash any changes before updating.

Commit the changed files into your git repository and the message will disappear.
Likely an enforced checkpoint

Kolahzary · 2019-06-13T10:17:21Z

It also happened to me, solved it by these steps

remove node_modules and package-lock.json
ng update @angular/core
ng update @angular/cli

The language within the message specifies that update all will _try_ to update all the packages. In practice and especially for larger projects, this operation will mostly likely not succeed. This can lead to the users attempting to use the all option with the force option which has a decent probability to break the project via incorrect peer dependency installation or other incompability version increases (packages that don't follow semver, for instance). Reference: angular#14561 (comment)

The language within the message specifies that update all will _try_ to update all the packages. In practice and especially for larger projects, this operation will mostly likely not succeed. This can lead to the users attempting to use the all option with the force option which has a decent probability to break the project via incorrect peer dependency installation or other incompability version increases (packages that don't follow semver, for instance). Reference: #14561 (comment)

salemdar · 2019-06-14T06:19:12Z

The problem is, usually Angular follows new Typescript releases from a few months behind and once there is a new Typescript version, ng update --all becomes unusable. The only solutions that I can think are adding an option to:

Add an option to skip updating incompatible dependencies:

ng update --all --skipIncompatible

Add an option to exclude some dependencies:

ng update --all --except typescript

madalinignisca · 2019-06-21T19:04:40Z

yarn add -D typescript@~3.4.0 sorted the problem.

For the moment, typescript will be updated to latest patch on 3.4.x versions. When Angular will allow latest stable typescript, I will update again it using the same command for the new supported minor version.

alan-agius4 · 2019-07-04T11:30:38Z

Duplicate of #13095

Sirjiskit · 2019-08-22T17:08:20Z

I once face the same issue was www.allovermyhead.com tried almost every thing getting one error of the other then i tried ng update --all --force;
Done evering was alright.

marc-wilson · 2019-08-22T17:16:50Z

Seems like ng update is just getting more finicky and fragile with every release.

angular-automatic-lock-bot · 2019-09-22T08:02:38Z

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.}

alan-agius4 added comp: schematics/update severity3: broken labels May 29, 2019

ngbot bot modified the milestone: needsTriage May 29, 2019

alan-agius4 added the freq3: high label May 29, 2019

alan-agius4 modified the milestones: needsTriage, 8.0.1 May 29, 2019

alan-agius4 mentioned this issue May 29, 2019

Re-running migration produces "invalid version" error #14559

Closed

clydin mentioned this issue Jun 13, 2019

fix(@schematics/update): remove update all suggestion message #14760

Merged

alan-agius4 modified the milestones: 8.0.x, 8.1.x Jul 2, 2019

alan-agius4 marked this as a duplicate of #13095 Jul 4, 2019

alan-agius4 closed this as completed Jul 4, 2019

wy193777 mentioned this issue Aug 10, 2019

ng update doesn't work every single time #15296

Closed

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 22, 2019

Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.1.1 <3.3", would install "3.4.5"). #14561

Package "@angular/compiler-cli" has an incompatible peer dependency to "typescript" (requires ">=3.1.1 <3.3", would install "3.4.5"). #14561

Comments

jtsom commented May 29, 2019

🐞 Bug report

Command (mark with an x)

Is this a regression?

Description

🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

jtsom commented May 29, 2019

alan-agius4 commented May 29, 2019 • edited Loading

jtsom commented May 29, 2019

jtsom commented May 29, 2019

alan-agius4 commented May 29, 2019

jtsom commented May 29, 2019

alan-agius4 commented May 29, 2019

marc-wilson commented May 29, 2019 • edited Loading

tc9011 commented May 30, 2019

alan-agius4 commented May 30, 2019 • edited Loading

tc9011 commented May 30, 2019

kswarthout commented May 30, 2019

TomySmit commented May 30, 2019

RogierdeRuijter commented May 30, 2019

huyinghuan commented May 31, 2019

damingerdai commented May 31, 2019 • edited Loading

KylerJohnson26 commented May 31, 2019 • edited Loading

tc9011 commented Jun 1, 2019

Laurens-makel commented Jun 1, 2019

matheo commented Jun 1, 2019 • edited Loading

damingerdai commented Jun 2, 2019

jtsom commented Jun 2, 2019

fr0 commented Jun 4, 2019 • edited Loading

marc-wilson commented Jun 4, 2019

fr0 commented Jun 4, 2019

marc-wilson commented Jun 4, 2019 • edited Loading

astronaute77 commented Jun 9, 2019

Random90 commented Jun 10, 2019

kishore0207 commented Jun 11, 2019 • edited Loading

deeja commented Jun 11, 2019

Kolahzary commented Jun 13, 2019

salemdar commented Jun 14, 2019

madalinignisca commented Jun 21, 2019

alan-agius4 commented Jul 4, 2019

Sirjiskit commented Aug 22, 2019

marc-wilson commented Aug 22, 2019

angular-automatic-lock-bot bot commented Sep 22, 2019

Command (mark with an `x`)

alan-agius4 commented May 29, 2019 •

edited

Loading

marc-wilson commented May 29, 2019 •

edited

Loading

alan-agius4 commented May 30, 2019 •

edited

Loading

damingerdai commented May 31, 2019 •

edited

Loading

KylerJohnson26 commented May 31, 2019 •

edited

Loading

matheo commented Jun 1, 2019 •

edited

Loading

fr0 commented Jun 4, 2019 •

edited

Loading

marc-wilson commented Jun 4, 2019 •

edited

Loading

kishore0207 commented Jun 11, 2019 •

edited

Loading