You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Migration failed: 404 Not Found - when upgrading angular project in a monorepo #26311
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
I have a monoripo project which contains both apps and libs. The libraries are not published on npm. When running the ng update command I am getting the following error:
Migration failed: 404 Not Found - GET https://registry.npmjs.org/@oogaday%2fshared - Not found
oogaday-shared is a shared library that I am using for my project.
Woraround: remove the lib dependancy and bring it back again after the update.
Minimal Reproduction
Create a monoripo with dependancy on a local package that is not published on npm.
changed the title [-]Migration failed: 404 Not Found - when upgrading angular project in a monoripo[/-][+]Migration failed: 404 Not Found - when upgrading angular project in a monorepo[/+]on Nov 10, 2023
Activity
[-]Migration failed: 404 Not Found - when upgrading angular project in a monoripo[/-][+]Migration failed: 404 Not Found - when upgrading angular project in a monorepo[/+]alan-agius4 commentedon Nov 10, 2023
ng updatedoes not supportyarn workspaces. See: #14841vlio20 commentedon Nov 10, 2023
@alan-agius4 it is not a yarn workspace. It is an npm workspace.
https://docs.npmjs.com/cli/v7/using-npm/workspaces
alan-agius4 commentedon Nov 10, 2023
Ah sorry you are right. Although there are the same concept.
angular-automatic-lock-bot commentedon Dec 11, 2023
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.