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.

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

See original GitHub issue

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

Issue Analytics

State:
Created 3 years ago
Reactions:7
Comments:16 (4 by maintainers)

Top GitHub Comments

4reactions

alan-agius4commented, Jul 10, 2020

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

2reactions

kyliaucommented, Jul 10, 2020

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/cli@9.1.11
+v9-lts: @angular/pwa@0.901.11
+v9-lts: @angular-devkit/architect@0.901.11
+v9-lts: @angular-devkit/architect-cli@0.901.11
+v9-lts: @angular-devkit/build-angular@0.901.11
+v9-lts: @angular-devkit/build-ng-packagr@0.901.11
+v9-lts: @angular-devkit/build-optimizer@0.901.11
+v9-lts: @angular-devkit/build-webpack@0.901.11
+v9-lts: @angular-devkit/core@9.1.11
+v9-lts: @angular-devkit/schematics@9.1.11
+v9-lts: @angular-devkit/schematics-cli@0.901.11
+v9-lts: @ngtools/webpack@9.1.11
+v9-lts: @schematics/angular@9.1.11
+v9-lts: @schematics/schematics@0.901.11
+v9-lts: @schematics/update@0.901.11

Top Results From Across the Web

Npm updates sucessfully, but still shows old version

sudo npm install npm@latest -g still npm -v showing you the older version, once try to close your terminal and open a new...

Click on a version number to view a previous ...

Tip: Click on a version number to view a previous version's package page. Current Tags. Version. Downloads (Last 7 Days).

Unable to resolve dependency tree error in Angular while ...

When using npm 7, Unable to resolve dependency tree errors comes up a lot because peer dependencies issues are treated as errors in...

Prevent npm install for not supported Node.js versions

Use a local npm configuration to prevent users from installing your module/project with an unsupported Node.js version.

Critical Issues Addressed in PAN-OS Releases

Bugs Affected Platform(if any). /Affected Version Description (release note) PAN‑92564 8.0.0‑8.0‑8, 8.1.0 PAN‑86882 8.0.0‑8.0.7. and all older Mainlines PAN‑81990 PA‑5220,PA‑5250. /. 8.0.4 Multiple DP restarts by...