SebastianVerified account

Can you give some examples of what yarn can't do and npm can, I'm curious to learn about that :)

most of this is around reliability: npm can automatically detect unexpected changes in node_modules, autorecover from cache corruption, etc

(it's also able to guarantee you get the same tree between two different installs. yarn's guarantees around this are notably weaker)

you can see it as a tradeoff: npm might usually be slightly slower, but it does a lot more work. yarn prioritizes speed over reliability.

> yarn prioritizes speed over reliability This isn't really true. Yarn was originally started to ensure deterministic installs.

It has been and continues to be the main focus.

Yet Yarn trusts way more of its system, for the sake of performance. Cache corruption is undetectable. :\

Only direct user modification of the cache can cause corruption. Yarn's cache is atomic. .yarn-metadata.json is verified for existence...