Support pnpm 11 (lockfile v9)#434
Open
j2ghz wants to merge 5 commits into
Open
Conversation
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
1 participant
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.
I copy-pasted the pnpm/ test into pnpm-11/, and added the
devEnginesfield to trigger pnpm to generate a multi-document yaml lockfile. Then I changed the yaml parsing code to handle that scenario. I used a quick and dirtyversion.test.ts, the plan would be to remove it and squash commits.There seems to be some naming confusion in the repo as to what v9 means, the code says
pnpm lockfile v9when it meanspnpm v9 with lockfile v6. I left most of it unchanged to keep the PR small, let me know if you want it standardized either way (name it according to lockfile (version 6 and 9), or according to pnpm (version 9 and 11).