feat: support transitive injected dependency #19
Merged
Conversation
This file contains 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
octogonz
reviewed
Mar 25, 2024
octogonz
reviewed
Mar 25, 2024
octogonz
reviewed
Mar 25, 2024
octogonz
approved these changes
Mar 25, 2024
octogonz
reviewed
Mar 25, 2024
octogonz
reviewed
Mar 25, 2024
octogonz
reviewed
Mar 25, 2024
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.
Summary
This PR to support transitive injected dependency situation.
Details
When we were working on supporting PNPM injected install feature for Rush Subspace, we got a conclusion that if a package gets installed in the injected way then every workspace:* dependency of that package also gets injected. (See more details on this PR)
This means, for all dependencies all that dependency chain, we need to generate the
.pnpm-sync.jsonfor them, to make the installation and build behavior correct.