npm 5 is out!
- Faster
- Indentation is preserved for package.json
- `--save` is default
- No more corrupt cache
- Offline mode
- Lockfile
-
-
-
If Yarn could do the things npm users need to do, then it could've been :)
3 replies 0 retweets 7 likes -
Replying to @zkat__ @maybekatz and
Can you give some examples of what yarn can't do and npm can, I'm curious to learn about that :)
1 reply 0 retweets 0 likes -
Replying to @alanzanattadev @nsisodiya and
most of this is around reliability: npm can automatically detect unexpected changes in node_modules, autorecover from cache corruption, etc
2 replies 0 retweets 2 likes -
Replying to @zkat__ @alanzanattadev and
(it's also able to guarantee you get the same tree between two different installs. yarn's guarantees around this are notably weaker)
3 replies 0 retweets 1 like -
Replying to @zkat__ @alanzanattadev and
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.
2 replies 0 retweets 1 like -
Replying to @zkat__ @maybekatz and
> yarn prioritizes speed over reliability This isn't really true. Yarn was originally started to ensure deterministic installs.
1 reply 0 retweets 4 likes
It has been and continues to be the main focus.
-
-
Replying to @sebmck @alanzanattadev and
Yet Yarn trusts way more of its system, for the sake of performance. Cache corruption is undetectable. :\
2 replies 0 retweets 0 likes -
Replying to @zkat__ @maybekatz and
Only direct user modification of the cache can cause corruption. Yarn's cache is atomic. .yarn-metadata.json is verified for existence...
1 reply 0 retweets 0 likes - 7 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 