Angular-cli: latest ver of npm is incorrect. It's 9.1.11 instead of 10.0.2

[eun-choi]

latest ver of npm is incorrect. It's 9.1.11 instead of 10.0.2

@angular/cli
9.1.11 • Public • Published 4 hours ago
Tip: Click on a version number to view a previous version's package page
Current Tags
9.1.11
latest
10.1.0-next.0
next
6.2.9
v6-lts
8.3.28
v8-lts
7.3.10
v7-lts
9.1.10
v9-lts
Version History

9.1.11
4 hours ago
10.0.2
4 hours ago
10.1.0-next.0
4 hours ago
9.1.10
8 days ago
10.0.1
8 days ago

[Splaktar]

Right, the latest tag on NPM should point to 10.0.2.

[changhuixu]

ng update command doesn't update to v10 now...

[napei]

Can concur. yarn global add @angular/cli installs 9.1.11

[daniloff200]

Yeah, I've got errors now, when try to build with the latest version, like

This version of CLI is only compatible with Angular versions 0.0.0 || ^9.0.0-beta || >=9.0.0 <10.0.0,
but Angular version 10.0.3 was found instead.

[miguellira]

@daniloff200 10.0.3? I was expecting a release of both 9.1.12 and 10.0.3 with a proper latest tag but neither been published to NPM. What version of Angular are your referencing in your package.json?

[daniloff200]

@miguellira I'm not specifically referencing 10+ version, but, have some jobs on my ci, which install latest & next versions of angular, to make sure, that library will work correct with them

in the Latest case, it was like

@angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ [email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @angular/[email protected]
+ @schematics/[email protected]
+ @angular/[email protected]

Same story happened with @schematics/angular

I also checked, that that should be cli version like 10.0.2, that's okay, but this error says, that version like 9.1.11 is only for < 10

[alan-agius4]

Hi all, we aware of the issue and will be addressed once a Googler in the US will be available to update tags of the packages. (Currently it's still 4:33am).

Points of action:

• Update latest tag to point to v10.0.2
• Update v9-lts tag to point to v9.1.10

$ for pkg in @angular/{cli,pwa} @angular-devkit/{architect,architect-cli,build-optimizer,build-ng-packagr,build-angular,build-webpack,core,schematics,schematics-cli} @ngtools/webpack @schematics/{angular,schematics,update}; do echo "\n$pkg"; npm dist-tag ls $pkg; done

@angular/cli
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 6.2.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@angular/pwa
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/architect
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/architect-cli
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-optimizer
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-ng-packagr
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-angular
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/build-webpack
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@angular-devkit/core
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 0.8.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@angular-devkit/schematics
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 0.8.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@angular-devkit/schematics-cli
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@ngtools/webpack
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 6.2.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@schematics/angular
latest: 9.1.11
next: 10.1.0-next.0
v6-lts: 0.8.9
v7-lts: 7.3.10
v8-lts: 8.3.28
v9-lts: 9.1.10

@schematics/schematics
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

@schematics/update
latest: 0.901.11
next: 0.1001.0-next.0
v6-lts: 0.8.9
v7-lts: 0.13.10
v8-lts: 0.803.28
v9-lts: 0.901.10

[miguellira]

@daniloff200 Got it. Looks like the latest NPM tag of other Angular libraries are valid where as the @angular/cli NPM tags were not bumped when 10.0.3 and 9.1.12 was released. For now I've pegged everything to 10.0.2. Hoping this gets resolved soon. Thanks.

[daniloff200]

@alan-agius4 heeey!
Thanks for your info!

I also saw, that the same issue with the version happened with @angular-devkit/core, @angular-devkit/schematics and @schematics/angular. Should I create a separate issue, to track that, or, it's the all the same part of already reported one?

[alan-agius4]

I also saw, that the same issue with the version happened with @angular-devkit/core, @angular-devkit/schematics and @schematics/angular. Should I create a separate issue, to track that, or, it's the all the same part of already reported one?

All Angular CLI packages are effected by this, this includes @schematics/* and @angular-devkit/ etc.. so no need to open a new issue.

[StephenFluin]

One of the workarounds if you are trying to ng update right now is to run ng update @angular/core@10 @angular/cli@10

[adhivenkatesh]

One of the workarounds if you are trying to ng update right now is to run ng update @angular/core@10 @angular/cli@10

But after updating unable to run ng serve --o getting below error :

An unhandled exception occurred: NGCC failed.
See "C:\Users\Admin\AppData\Local\Temp\ng-2cVol4\angular-errors.log" for further details.

[kyliau]

Sorry about this! I've retagged all CLI packages, with latest = v10.0.2.

$ ./bin/devkit-admin dist-tag --version 10.0.2 --tag latest
+latest: @angular/[email protected]
+latest: @angular/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @angular-devkit/[email protected]
+latest: @ngtools/[email protected]
+latest: @schematics/[email protected]
+latest: @schematics/[email protected]
+latest: @schematics/[email protected]

[adhivenkatesh]

Yes got resolved by putting the below items in to .src/tsconfig.json

thanks for the response.

"angularCompilerOptions": {
"enableIvy": false
},

[kyliau]

I've also retagged v9-lts to point to v9.1.11

$ ./bin/devkit-admin dist-tag --version 9.1.11 --tag v9-lts
+v9-lts: @angular/[email protected]
+v9-lts: @angular/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @angular-devkit/[email protected]
+v9-lts: @ngtools/[email protected]
+v9-lts: @schematics/[email protected]
+v9-lts: @schematics/[email protected]
+v9-lts: @schematics/[email protected]

[angular-automatic-lock-bot[bot]]

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