chore: upgrade pnpm lockfile to v9 #10
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
qbtf
force-pushed
the
chore/upgrade-pnpm-lockfile-to-v9
branch
from
ce1fb93
to
3ce833f
Compare
|
This PR has been force-pushed to account for the recent release in the main branch, including removing two |
WeiYiChiuAtTonfura
approved these changes
Oct 23, 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
When trying to build the project, I noticed that my pnpm v8 could not resolve the lock file with:
This patch upgrades the lock file in two steps, one to lockfile v6, and the other to v9. Nx can also understand this new schema.
Ticket(s)
N/A
Type of change
Please delete options that are not relevant.
Screenshot(s)
Test Steps
Reference Document(s)
The lockfile version 5.4 is unsupported by pnpm: pnpm/4.
nx's support: nx#22906.
Checklist