4 ms·
Meh; unless you're doing something really complex or ran into an odd bug, npm is fine and so is yarn. They're both fast and stable enough and they both do _basi
by BinaryIdiot 8y ago
Meh; unless you're doing something really complex or ran into an odd bug, npm is fine and so is yarn. They're both fast and stable enough and they both do _basically_ the same thing.
I don't understand the turf war; the node module ecosystem is incredibly shitty (good luck running any modern framework without pulling in hundreds of dependencies) and these two tools do basically the same thing. Just use whichever one works ¯\_(ツ)_/¯
- pg_bot 8y agoYMMV but in my experience npm would break consistently doing the most trivial of tasks. Switched to yarn and haven't once looked back.
- manigandham 8y agoMeh? NPM only started to get better after yarn was released so this is over several years of experience. Yarn also solved major speed and reliability issues. I'm not sure why that keeps being glossed over but NPM often had problems with reproducible builds and generally keeping things working. Just check the top comment on this page to see the outstanding bugs.
- agnivade 8y agoDude, I can't even begin to start counting how many times I have had to rm -rf the node_modules/ folder and do an npm install afresh, just because some dependency has screwed up the other. yarn has given me peace that I did not think was possible.