Why should we use pnpm?

at www.kochan.io

17 up and 2 down, posted by zkochan 2557 days ago 9 comments

zkochan 2557 days ago. link parent 1 point ▲ ▼

Try it for sure and if you have any issues feel free to file issues on github.

We have our own shrinkwrap.yaml file that looks like this: https://github.com/pnpm/node-package-manager-benchmark/blob/master/shrinkwrap.yaml

We have no plans currently to support yarn.lock. I can imagine someone might come up with a yarn.lock/shrinkwrap.yaml converter in the future

Replies

blai 2556 days ago. link 1 point ▲ ▼

shrinkwrap.yaml is in fact way easier to read and understand, I really like it. Having said that, it is a lot easier to sell the idea of replacing NPM with Yarn than replacing NPM with pnpm. Any way you can push Yarn to adopt the pnpm approach?

zkochan 2556 days ago. link 3 points ▲ ▼

TBH I would prefer merging pnpm to npm instead. I don't see any reason to further promote Yarn which is already overrated.

The concept of linking packages existed long before Yarn. First commit to Yarn was on Jan 23, 2016.

The concept of linking packages was introduced by Alexander Gugel in the ied package, first commit on Aug 6, 2015.

Approximately half year later Rico Sta. Cruz has created pnpm which was pretty similar to ied but with better npm compatibility.

Creators of Yarn did know about the possibility to use symlinks and links. You can search in their repo for discussions about it. They discussed the possibility of using symlinks back when Yarn was not public and due to many reasons decided not to use symlinks.