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
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.
The text was updated successfully, but these errors were encountered:
alan-agius4
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
Nov 10, 2023
Command
update
Is this a regression?
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.
This is how the monorepo package.json looks like:
And this is how the webapp package.json looks like:
Exception or Error
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: