Fix force resolved versions for transitive local dependencies #3691
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.
Previously we were pre-populating managed dependencies with only the first level of dependencies from roots. Now we will do this before attempting to load manifests to ensure this works recursively.
Motivation:
Make the force resolved versions mode work for cases where local dependencies are used in packages other than the roots.
Modifications:
_resolveToResolvedVersion
loadDependencyManifests
to enable automatically adding local packages to managed dependencies if we are in the force resolved versions modeI considered two alternative changes:
Result:
The force resolved versions mode works for cases where local dependencies are used in packages other than the roots.