-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ng update fails when using local library #13059
Comments
Hi, when you say local package? is it in a private npm repo? or using the |
it's
|
@alan-agius4 I have the same issue with a private npm repo. When I update any node module it says that it can't find my private module (which is on my private repo) on npmjs.org. This was working until cli version 7.0.7 |
Fix previously described in this comment relates to another issue, sorry. |
That’s a different problem. Local packages; as well as git packages are not suppported by ‘ng update’ currently. |
Even with CLI 7.1.1 I still have the issue. Here is my config: Angular CLI: 7.1.1 Package Version@angular-devkit/architect 0.11.0 [08:41:24][~/Documents/devs/my-project/frontend]$ ng update |
Same problem here.
Where private-pkg is a package stored in a Nexus repository.
|
Same problem here.
Result
Where private-pkg is a package stored in a ProGet repository. ng update worked in the same scenario with angular-cli in Angular 6 My private package has also a "publishConfig": {
"registry": "https://proget.myserver.de/npm/MYFEED"
}, |
In latest release, 7.1.3, the problem seems that has been fixed. |
@elboukhari would you try 7.1.3 and verify if the issue still persists? |
Hi @mgechev I still have the same issue even under 7.1.3 !
And here is the declaration of the lib in my package.json :
where "MY-LIB" is my local lib |
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:
Actually for a workaround i have to uninstall all my local repo packages then run |
I'm getting this on @angular packages with 7.1.3. The package is different each time I run it but it's typically angular packages. |
I am using a private npm repository and my dependencies are declared this way:
|
This issue still exists in Version @angular/cli 7.3.2 |
This is still happening with @angular/cli 7.3.6 $ ng update
Cannot read property '0.7.2' of undefined $ ng version
_ _ ____ _ ___
/ \ _ __ __ _ _ _| | __ _ _ __ / ___| | |_ _|
/ △ \ | '_ \ / _` | | | | |/ _` | '__| | | | | | |
/ ___ \| | | | (_| | |_| | | (_| | | | |___| |___ | |
/_/ \_\_| |_|\__, |\__,_|_|\__,_|_| \____|_____|___|
|___/
Angular CLI: 7.3.6
Node: 8.11.4
OS: linux x64
Angular: 7.2.4
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker
Package Version
-----------------------------------------------------------
@angular-devkit/architect 0.13.0
@angular-devkit/build-angular 0.13.0
@angular-devkit/build-optimizer 0.13.0
@angular-devkit/build-webpack 0.13.0
@angular-devkit/core 7.3.6
@angular-devkit/schematics 7.3.6
@angular/cdk 7.3.1
@angular/cli 7.3.6
@angular/material 7.3.1
@ngtools/webpack 7.3.0
@schematics/angular 7.3.6
@schematics/update 0.13.6
rxjs 6.4.0
typescript 3.2.4
webpack 4.29.0 In
|
For me this issue is fixed in version 7.3.9. I didn't test earlier versions. I am using a private npm repository (that had the same issue since version 7.0.7) for some node modules, not a local path.
|
Tested in 8.0.3 and not working. |
I recently updated from Angular 7.2.15 and angular-cli 7.3.9 to Angular 8.0.0 and angular-cli 8.0.2. I used Disclaimer: I don't have a path to a file for my custom node modules. I have a private repository with my custom modules that also serves all modules from |
I'm having the same issue with a local module that is being pointed to via a path. Upgrade from 6 to 7 worked fine so perhaps this is a regression? |
This drives me nuts every time there is a major version bump. Could there not be an option similar to |
…gular#13059) Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or Git references will now be skipped during the update process.
Fixes angular#13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or Git references will now be skipped during the update process.
Fixes angular#13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or Git references will now be skipped during the update process.
Fixes angular#13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or Git references will now be skipped during the update process.
Fixes angular#13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or Git references will now be skipped during the update process.
Fixes angular#13059. Non-NPM dependencies in package.json are now filtered out of `ng update`. Dependencies which are linked as tarball or Git references will now be skipped during the update process.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an x)
Command (mark with an x)
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
The text was updated successfully, but these errors were encountered: