feat(manager/npm): extract contraints again on post-update #23131
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.
Changes
package.json
instead of usingextractedContraints
.constraints
are now consistently preferred after updates.Before this PR post-update has relyed on
extractedContraints
which comes from first update in PR.So if you group different manager updates it can fail because the
extractedContraints
from wrong manager are used.See linked PR and the history of it for working sample for yarn.
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: