3 ms·
For me the biggest advantage of using pnpm is that it doesn't fill up my hard disk. From their main page - "Files inside node_modules are cloned or hard linke
by thunderbong 4y ago
For me the biggest advantage of using pnpm is that it doesn't fill up my hard disk.
From their main page -
"Files inside node_modules are cloned or hard linked from a single content-addressable storage'
- rektide 4y agoYarn also does this very well & pioneered reconsidering how we store stuff, I believe. But they broke the universe when they switched it on by default in v2, in ways I'm not intimate with. v3 maybe possibly makes things somewhat better[1], started looking at ways to be flexible/allow different strategies. I do care about speed a good bit, as I've seen more big monorepos happen. At first I was a bit sad that Yarn v2+/pnp was beating Pnpm "with cache, with lockfile" by so much, but pnpm's "with node_modules, with lockfile" is basically the same speed. The first is more the "get started with cache" case (and what yarn v2+/pnp does every time there there-out), but the second is what most day to day dev really is: the speed converges totally in the day to day. A zoom in on the graph might reveal some differences perhaps; looks like ~2s, which is a small bar on this graph. Also pnpm is like 2x as fast if you don't have cache, so actual first install win may well go to pnpm again. [1] https://dev.to/arcanis/yarn-3-0-performances-esbuild-better-patches-e07 https://dev.to/arcanis/yarn-3-0-performances-esbuild-better-...