From a StackShare Community member: “I’m a freelance web developer (I mostly use Node.js) and for future projects I’m debating between npm or Yarn as my default package manager. I’m a minimalist so I hate installing software if I don’t need to- in this case that would be Yarn. For those who made the switch from npm to Yarn, what benefits have you noticed? For those who stuck with npm, are you happy you with it?"
As far as I know Yarn is a super module of NPM. But it still needs npm to run.
Yarn was developed by Facebook's guys to fix some npm issues and performance.
If you use the last version of npm most of this problem does not exist anymore.
You can choose the option which makes you more confortable. I like using yarn because I'm used to it.
In the end the packages will be the same. Just try both and choose the one you feel more confortable. :)
We use Yarn because it allows us to more simply manage our node_modules. It also simplifies commands and increases speed when installing modules. Our teams module download time was cut in half after switching from NPM to Yarn. We now require all employees to use Yarn (to prevent errors with package-lock.json and yarn.lock).
We recently made the switch to Yarn mostly because of workspaces, speed, and the features in the Yarn v2 release. It has been great.
