use Yarn

npm is a piece of software which is quite possibly beyond repair. Yarn strikes me as a well-considered, sane piece of software. I ❤️ that yarn is deterministic, whereas npm install can produce different directory structures given different starting states.

I can think of three ways to use Yarn:

• have make setup run npm install yarn then yarn;
• rely on a globally installed yarn (as we currently do with npm); or
• support NPM=/path/to/global/yarn make setup.

Does anyone have a preference for one of these three options?

[Avaq]

It looks like yarn is quite similar to ied. Ied is a Nix-inspired package manager for NodeJS which has worked quite well for me. It seems to have all the same guarantees as yarn, and creates a completely flat structure using symlinks. However, it has no support for committing any kind of caches.

[davidchambers]

I’d be happy to do a PR if that’s the route we want to go.

I would like to see this! 😃