-
Notifications
You must be signed in to change notification settings - Fork 89
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
Switch package manager to pnpm
#1660
Comments
Hello, I saw discussion here, but I answer in this issue for an easier traceability with community: I'm not sure this change is worth it. We would like to keep what is working and yarn is not deprecated and still widely used. We want to avoid pain and work in order to focus on the most critical things. I'm afraid of the new pains this huge change could bring. However I agree with you @flevi29, updating yarn could be a good move Would love to have the opinion of the community of this |
I'm not so sure about this huge pain and work. I detailed in the PR in my last comment that this will not be the case because of how Anyhow, the way I see it, to upgrade you'll still need to change |
Alright fair enough, switching to |
Closed in favour of #1664. |
A lot of high profile repositories these days use
pnpm
.The list goes on.
We could just upgrade
yarn
, but I am more familiar withpnpm
and I generally see thatpnpm
is more popular these days, although their latest version is not on npmjs, so it's not really trackable. Speed seems to be on par, withpnpm
having a slight edge perhaps (https://pnpm.io/benchmarks) https://p.datadoghq.eu.Lockfile can be transformed.
We can also use the latest and greatest
corepack
features of Node.js.The text was updated successfully, but these errors were encountered: