2 ms·
Also ran some numbers here (with warm cache. node 6.10.3). * yarn: 25s * npm@5: 28s * npm@4: 63s * npm@3: 68s So performance is now comparable, which
by gtirloni 9y ago
Also ran some numbers here (with warm cache. node 6.10.3).
* yarn: 25s
* npm@5: 28s
* npm@4: 63s
* npm@3: 68s
So performance is now comparable, which is awesome, but I'd still stick to yarn because we have been burned too many times by npm v2/v3 with call stack issues and other errors. I don't have the energy (or the time/faith) to go through that again.
Competition is wonderful though. I'll check npm again in 6-12 months and see what the community thinks of it before switching again.
- farskipper 9y agoamen