Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFC] Change yarn to pnpm #268

Open
simenandre opened this issue Apr 18, 2023 · 1 comment
Open

[RFC] Change yarn to pnpm #268

simenandre opened this issue Apr 18, 2023 · 1 comment

Comments

@simenandre
Copy link
Member

Main driver for me is:

  • pnpm config set auto-install-peers true (Automatically install peer dependencies, no need to keep maintaining it in our own package.json)
  • Less boilerplate in each repository (no .yarn folder)

As we're moving towards using tools like corepack, I no longer feel we need to pack the binary for our package manager with our code.

Personally not sure about this yet, but I want to request some comments.

@mrboen94
Copy link

One thing to consider is the compability, pnpm is great and ive had mostly no issues with it. Sometimes it seems to break on M1 macs though (but usually resolvable). Its a fine line to balance between what is best in theory and what is best in practise. I'd argue pnpm should wait just a little longer to see if the bug tracking in their repository calms down a bit.

This might be a good change to look further into around July/August as it seems to move pretty fast right now.

TL;DR: I think its the right direction, but I would personally wait a few months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants