angular-cli: ng update fails when using local library

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 node --version : v10.13.0 npm --version : 6.4.1 ng --version :

`Angular CLI: 7.1.0 Node: 10.13.0 OS: linux x64 Angular: 7.1.0 … animations, cdk, cli, common, compiler, compiler-cli, core … forms, http, language-service, material … material-moment-adapter, platform-browser … platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.11.0 @angular-devkit/build-angular 0.11.0 @angular-devkit/build-optimizer 0.11.0 @angular-devkit/build-webpack 0.11.0 @angular-devkit/core 7.1.0 @angular-devkit/schematics 7.1.0 @ngtools/webpack 7.1.0 @schematics/angular 7.1.0 @schematics/update 0.11.0 rxjs 6.3.3 typescript 3.1.6 webpack 4.26.1`

Repro steps just type : ng update

The log given by the failure Not found : XXXXXX ()

In my package.json this library is declared as :

I’m still having the issue even with : “@angular/cli”: “7.1.0”

the error is the same as in the previous comment: 404 Not Found - GET https://registry.npmjs.org/XXXXXXX - Not found

Desired functionality just ignore local libraries and update angular ones

Mention any other details that might be useful

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 4
Comments: 22 (2 by maintainers)

Commits related to this issue

fix(@angular-devkit/schematics): filters out non-NPM dependencies (#13059) Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or Git re... — committed to dgp1130/angular-cli by dgp1130 5 years ago
fix(@angular-devkit/schematics): filters out non-NPM dependencies Fixes #13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or ... — committed to dgp1130/angular-cli by dgp1130 5 years ago
fix(@angular-devkit/schematics): filters out non-NPM dependencies Fixes #13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or ... — committed to dgp1130/angular-cli by dgp1130 5 years ago
fix(@angular-devkit/schematics): filters out non-NPM dependencies Fixes #13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or ... — committed to dgp1130/angular-cli by dgp1130 5 years ago
fix(@angular-devkit/schematics): filters out non-NPM dependencies Fixes #13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or ... — committed to dgp1130/angular-cli by dgp1130 5 years ago
fix(@angular-devkit/schematics): filters out non-NPM dependencies Fixes #13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or ... — committed to dgp1130/angular-cli by dgp1130 5 years ago
fix(@angular-devkit/schematics): filters out non-NPM dependencies Fixes #13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or ... — committed to angular/angular-cli by dgp1130 5 years ago

Most upvoted comments

it’s file:// protocol, here is the corresponding line in package.json :

"MY-AWeSOME-LOCAL-LIB": "file:lib/MY-AWeSOME-LOCAL-LIB.tgz",

elboukhari on Nov 27, 2018

Same problem here.

$ ng update 404 Not Found - GET https://registry.npmjs.org/private-pkg - Not found

Where private-pkg is a package stored in a Nexus repository.

ng update worked in the same scenario with angular-cli before 7.1.0.

beleta on Dec 4, 2018

Fix previously described in this comment relates to another issue, sorry. Thanks to @clydin who mentioned this. 😃

denisoby on Nov 30, 2018

Tested in 8.0.3 and not working.

Kim-Andersen on Jun 17, 2019

For me with ProGet Package the error also still exists with 7.1.3

EDIT:

The package is registered in the package-lock.json file as followed:

"@my/my-package": {
  "version": "7.1.2",
  "resolved": "https://proget.myserver.de/npm/MYFEED/@my/my-package/-/my-mypackage-7.1.2.tgz",
  "integrity": "sha1-GXeQ7XsDxhUAlCZMw0OYFCBrK0Y=",
  "requires": {
    "@aspnet/signalr": "^1.1.0",
    "tslib": "^1.9.0"
  }
},

Actually for a workaround i have to uninstall all my local repo packages then run ng update and then after that reinstall my local packages.

JohnnyDevNull on Dec 18, 2018

Even with CLI 7.1.1 I still have the issue.

Here is my config: `[08:41:18][~/Documents/devs/my-project/frontend]$ ng version

Angular CLI: 7.1.1 Node: 10.13.0 OS: linux x64 Angular: 7.1.1 … animations, cli, common, compiler, compiler-cli, core, forms … http, language-service, platform-browser … platform-browser-dynamic, router

Package Version

@angular-devkit/architect 0.11.0 @angular-devkit/build-angular 0.11.0 @angular-devkit/build-optimizer 0.11.0 @angular-devkit/build-webpack 0.11.0 @angular-devkit/core 7.1.0 @angular-devkit/schematics 7.1.1 @angular/cdk 7.1.0 @angular/material 7.1.0 @angular/material-moment-adapter 7.1.0 @ngtools/webpack 7.1.0 @schematics/angular 7.1.1 @schematics/update 0.11.1 rxjs 6.3.3 typescript 3.1.6 webpack 4.26.1

[08:41:24][~/Documents/devs/my-project/frontend]$ ng update 404 Not Found - GET https://registry.npmjs.org/xxx-xxx-xxx - Not found `

elboukhari on Dec 4, 2018