Migrate from yarn 1.x to pnpm #5084
Merged
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
Turbo87
added
A-frontend 🐹
C-internal 🔧
Turbo87
force-pushed
the
pnpm
branch
3 times, most recently
from
450a267 to
7ba83a3
Compare
|
☔ The latest upstream changes (presumably a567f95) made this pull request unmergeable. Please resolve the merge conflicts. |
This should allow us to use pnpm instead of yarn
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.
https://pnpm.io/ is a different package manager for JS code, similar to yarn and npm. Its main advantage is saving a lot of disk space if a developer has multiple projects using similar dependencies, because it only stores a single copy of each dependency version on the disk, instead of one-per-project. This ultimately also leads to small speed savings.
I've been successfully using pnpm for a while on several other projects and it's been working quite well so far.
The main downside for us is that the official Heroku Node.js buildpack does not support pnpm (yet). That means we need to use an unofficial buildpack that does support it. We're using an unofficial buildpack for Rust too though, so I'm not too worried about the security implications and the pnpm buildpack appears to be maintained by a legitimate company.