Run pnpm dedupe#1746
Merged
Merged
Conversation
Member
|
I thought pnpm deduped by default nowadays? |
pokey
approved these changes
Aug 8, 2023
auscompgeek
commented
Aug 8, 2023
Member
Author
🤷 I don't think it'll try to update existing locked transitive dependencies, but will reuse existing resolutions. Both pnpm and yarn behave this way I think. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
#1745 is almost impossible to review 😅
I'd suggest running
pnpm dedupeon the PR but it turns outmainhas a whole bunch of duplicate transitive deps too, so running it againstmainfirst.Checklist
I have added testsI have updated the docs and cheatsheet