3 ms·

Half-OT: What do you think of pnpm? I saw it off and on since 2015 and read some projects switched to it and then back again, when it didn't work out.

by k__ 3y ago

johnnypangs 3y ago
Coming from using yarn, it is way easier to move to pnpm than to yarn 2+. It’s now my go to. The only issues I find is that you’ll still not find good community support for it. Things like Dependabot and some edge hosting platform build agents.
- hammeiam 3y ago
  You can email the dependabot team and they'll opt your repo into a beta with pnpm support
- nwienert 3y ago
  Don't think this is true, yarn 2 is a drop in basically you may be thinking of the PnP stuff but that's off by default now. pnpm used to be the difficult one but seems a bit better these days.
- xiphias2 3y ago
  For me there was always problem with pnpm cache working together with vite when doing pnpm link, and yarn link works perfectly, so even though pnpm is much faster, I went back to yarn.
progx 3y ago
pnpm has only benefits if you use it with packages / workspaces and things like automatic patching. Use it in some projects, but for the most simplier projects i stay with simple npm and use scripts (via scripty). Install / update perfomance or SSD space saving are for me not really killer features.
mikojan 3y ago
From personal experience introducing pnpm into a big JavaScript project my very subjective(!) view of the situation: pnpm offers fast installs and the best dependency management capabilities I have seen. However, there is a steep learning-curve attached to the latter. You cannot just task a random developer with fixing emerging problems or else you will be left with half-a-dozen large and unintelligible config files and hacks. If you are the type of team that never updates dependencies, it is not worth the effort. If you are the type of team that applies the heuristic of "yes" to the question "Should I download a dependency?", it is not worth the effort. On the other hand, if you value build tool performance, if you are updating frequently and if your dependencies are carefully curated, pnpm is great and with Node >16 it is just a... $ corepack enable ...away, too.

Half-OT: What do you think of pnpm? I saw it off and on since 2015 and read some projects switched to it and then back again, when it didn't work out.

by k__ 3y ago

Half-OT: What do you think of pnpm? I saw it off and on since 2015 and read some projects switched to it and then back again, when it didn't work out.

johnnypangs 3y ago

Coming from using yarn, it is way easier to move to pnpm than to yarn 2+. It’s now my go to. The only issues I find is that you’ll still not find good community support for it. Things like Dependabot and some edge hosting platform build agents.

hammeiam 3y ago
You can email the dependabot team and they'll opt your repo into a beta with pnpm support
nwienert 3y ago
Don't think this is true, yarn 2 is a drop in basically you may be thinking of the PnP stuff but that's off by default now. pnpm used to be the difficult one but seems a bit better these days.
xiphias2 3y ago
For me there was always problem with pnpm cache working together with vite when doing pnpm link, and yarn link works perfectly, so even though pnpm is much faster, I went back to yarn.

progx 3y ago

pnpm has only benefits if you use it with packages / workspaces and things like automatic patching. Use it in some projects, but for the most simplier projects i stay with simple npm and use scripts (via scripty). Install / update perfomance or SSD space saving are for me not really killer features.

mikojan 3y ago

From personal experience introducing pnpm into a big JavaScript project my very subjective(!) view of the situation: pnpm offers fast installs and the best dependency management capabilities I have seen. However, there is a steep learning-curve attached to the latter. You cannot just task a random developer with fixing emerging problems or else you will be left with half-a-dozen large and unintelligible config files and hacks. If you are the type of team that never updates dependencies, it is not worth the effort. If you are the type of team that applies the heuristic of "yes" to the question "Should I download a dependency?", it is not worth the effort. On the other hand, if you value build tool performance, if you are updating frequently and if your dependencies are carefully curated, pnpm is great and with Node >16 it is just a... $ corepack enable ...away, too.