fix: pnpm v9 peer deps with workspace/link: deps #2179
Merged
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.


Add tests for the scenario fixed in a8c192e
Fix the issue when reproduced in pnpm v9+
FWIW I was trying to understand when this pnpm <v9
idfield is used and no tests failed when removing it. It seems it is declared in pnpm <v9 whenfile:orlink:dependencies have peer dependencies, theidwill be thefile:path without the peer dependency information.The ugly v9 workaround can be removed in #2177 but I wanted to add tests before that PR
Changes are visible to end-users: no
Test plan