refactor(@angular/cli): remove usage of npm-pick-manifest dependency #30784
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clydin
force-pushed
the
cli/remove-npm-pick-manifest
branch
2 times, most recently
from
fbf0f73 to
f764984
Compare
The amount of used functionality provided by the `npm-pick-manifest` package was minimal within the Angular CLI. Logic to determine an appropriate package version for `ng update` is similar to the logic in `ng add`. The later of which did not use the `npm-pick-manifest` package. To reduce the total amount of dependencies, the logic from `ng add` was repurposed to fit the requirements of `ng update`.
clydin
force-pushed
the
cli/remove-npm-pick-manifest
branch
from
f764984 to
8f160e8
Compare
clydin
added
the
action: review
alan-agius4
approved these changes
Jul 25, 2025
alan-agius4
added
action: merge
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The amount of used functionality provided by the
npm-pick-manifestpackage was minimal within the Angular CLI. Logic to determine an appropriate package version forng updateis similar to the logic inng add. The later of which did not use thenpm-pick-manifestpackage. To reduce the total amount of dependencies, the logic fromng addwas repurposed to fit the requirements ofng update.