Repository navigation
ng update breaks on "private" packages #28834
Description
Command
update
Description
I'm unsure if this is a regression. But when there is a "private" package in an angular project, ng update fails to run.
Minimal Reproduction
To reproduce:
# use an "old" version to get started
npx @angular/cli@18.1 new DemoPackageIssue
cd DemoPackageIssue
# add a package from the deno std library (not really private..)
npx jsr add @std/toml
# try to upgrade:
npx ng updateOr manually add the package to the package.json like this:
"dependencies": {
"@angular/animations": "^18.1.0",
...
"@std/toml": "npm:@jsr/std__toml@^1.0.1",
},
Exception or Error
Using package manager: npm
Collecting installed dependencies...
Found 28 dependencies.
✖ Migration failed: 404 Not Found - GET https://registry.npmjs.org/@std%2ftoml - Not found
See "/tmp/ng-f4tUqx/angular-errors.log" for further details.
Your Environment
I didn't test it with anything older as 18.0, but I suspect _all_ versions have this issue.
At least 19-rc.1 still has the problem
Anything else relevant?
This is an unneeded restriction. When there are packages in the package.json that Angular can't 'trace' it should be safe to ignore them. Erroring out is highly inconvenient.
Activity
antonioconselheiro commentedon Nov 14, 2024
This issue can be reproduced in this repository: https://github.com/antonioconselheiro/bug-ng-update-with-jsr-dependencies
Not only private packages, but any package from jsr throw error.
fix(@angular/cli): handles not found packages for ng-update
allout58 commentedon Jan 15, 2025
I've opened a PR that will gracefully skip packages if it can't pull the metadata from the registry. This doesn't help it find the registry (would be useful in the case of JSR), but at least lets you continue and you can manually upgrade those dependencies later.
eluchsinger commentedon Jun 21, 2025
The issue also affects us. Trying to upgrade from v19 to v20, the migration fails with a 404 not found, because it tries to locate our local package in the npmjs registry. Not sure what use case there is for this, but a way to skip this check would be nice.
We're using the turborepo way to link local packges.
tsteuwer-accesso commentedon Aug 25, 2025
This is also affecting us. We use something along the lines of this in our .npmrc:
mumenthalers commentedon Sep 16, 2025
affected as well.
passee commentedon Dec 9, 2025
this issue was opened more than a year ago and I dont see any progress on it.
whats the problem here and why does ng update for example not acknowledge a .npmrc file?
Edit:
the issue was, that i was in a wrong directory. while
npm istill worked because it seems like to check the parent folder too,ng updatedidnt see the npmrc filejohn8329 commentedon Mar 6, 2026
ng updatenever worked when there's packages in private repositories, namespaced or not. .npmrc is ignored. Just remove the packages as a workaround and re-add them later.ChristofFritz commentedon Mar 30, 2026
We're also affected. Any update on this?
fix(@angular/cli): gracefully skip unfetchable packages during ng update
fix(@angular/cli): handle npm-aliased and unfetchable packages in ng …
angular-automatic-lock-bot commentedon Jul 18, 2026
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.