-
Notifications
You must be signed in to change notification settings - Fork 12k
ng update
does not check package.json
versions
#17599
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
Comments
I'm hoping this will address some of the security warnings issued by GitHub. Generated this commit by running: $ (cd services/ng-frontend/ && ng update --all) This actually took a couple attempts, due to a bug in the CLI. Filed angular/angular-cli#17599 to look into it further.
I am not sure if this was by design or an oversight. @clydin would know more. I do believe that we should check the To re-run the migration you don’t need to delete the node_modules. You can use the Example
|
Duplicate of #16020 |
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
Command
Is this a regression?
Dunno.
Description
When
ng update
checks for the current version of packages, I believe it uses the version installed innode_modules/
and ignores the text inpackage.json
. This can cause missed updates in circumstances where a user updates a package, resets the update via VCS, then re-runs the update. Sincenode_modules/
is not cleared, the subsequentng update
run believes the package was already updated. Deletingnode_modules/
appears to fix the problem (though I have to run withng update --all
or else I hit some peer dep issues, but I think that's a separate problem).🔬 Minimal Reproduction
Fortunately I still have the logs from my terminal (with some inline comments about my reasonsing):
Migration log
The text was updated successfully, but these errors were encountered: