Late to the party, but can't wait for the technical write up on this. I think npm has been a headache for everyone at some point, which is one of the main reas

Late to the party, but can't wait for the technical write up on this. I think npm has been a headache for everyone at some point, which is one of the main reasons I started contributing to Yarn. I think npm has done a lot of good work in the past year to respond to the necessary change, so kudos to them for their work; however, it's nowhere near the rock-solid package manager that we need. If the Javascript ecosystem is to ever be taken seriously, and not as a toy -- it has to have more reliability. Ergonomically, I currently thing it's ahead of many other package managers because of how simple it is to get running. The number of "gotcha's" after npm install is nothing to shake a stick at, though. One of the things you can do to get builds that aren't as suspect to npm registry issues is configuring an offline mirror [1]. From the post: "Repeatable and reliable builds for large JavaScript projects are vital. If your builds depend on dependencies being downloaded from network, this build system is neither repeatable nor reliable. One of the main advantages of Yarn is that it can install node_modules from files located in file system. We call it “Offline Mirror” because it mirrors the files downloaded from registry during the first build and stores them locally for future builds." 1 - https://yarnpkg.com/blog/2016/11/24/offline-mirror/ https://yarnpkg.com/blog/2016/11/24/offline-mirror/