Echo JS 0.11.0

<~>
MaxArt 276 days ago. link 2 points
You know what, I could give it a try. I still am unconvinced by npm's decision to flatten the dependency tree, so I guess anothr approach is welcome.

Do you plan to support yarn.lock files as well?

Replies

xab 270 days ago. link 1 point
Without a flat tree npm on Windows was nearly unusable. I dont't want to blame npm or Windows or whoever, just saying that working in a cross platform environment was pretty painful and now it's much better.
blai 276 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 276 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.