René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"`ng update` breaks on \"private\" packages","articleBody":"### Command\n\nupdate\n\n### Description\n\nI'm unsure if this is a regression. But when there is a \"private\" package in an angular project, `ng update` fails to run. \n\n### Minimal Reproduction\n\nTo reproduce:\n```bash\n# use an \"old\" version to get started\nnpx @angular/cli@18.1 new DemoPackageIssue\ncd DemoPackageIssue\n# add a package from the deno std library (not really private..)\nnpx jsr add @std/toml\n# try to upgrade:\nnpx ng update\n```\n\nOr manually add the package to the `package.json` like this:\n```json\n  \"dependencies\": {\n    \"@angular/animations\": \"^18.1.0\",\n    ...\n    \"@std/toml\": \"npm:@jsr/std__toml@^1.0.1\",\n  },\n\n```\n\n\n### Exception or Error\n\n```text\nUsing package manager: npm\nCollecting installed dependencies...\nFound 28 dependencies.\n✖ Migration failed: 404 Not Found - GET https://registry.npmjs.org/@std%2ftoml - Not found\n  See \"/tmp/ng-f4tUqx/angular-errors.log\" for further details.\n```\n![Image](https://github.com/user-attachments/assets/49a95e7c-e5f3-4d8d-b338-a68cc47ab4b5)\n\n\n### Your Environment\n\n```text\nI didn't test it with anything older as 18.0, but I suspect _all_ versions have this issue. \nAt least 19-rc.1 still has the problem\n```\n\n### Anything else relevant?\n\nThis 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. ","author":{"url":"https://github.com/SanderElias","@type":"Person","name":"SanderElias"},"datePublished":"2024-11-11T06:11:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":9},"url":"https://github.com/28834/angular-cli/issues/28834"}