Needs advice

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?"

7 upvotes·181.6K views
Replies (14)
Principal Software Engineer at Socotra·

You should use whichever had the best DX (developer experience) for your team. If you are doing a massive front-end project, consider yarn if not only because it makes it a snap to go from zero to ready. What some people say about npm being more stable or easier for smaller projects is highly true as well. (not to mention, you sometimes have to install yarn) But, note that official NodeJS Docker images ship with both npm and yarn. If you want to use yarn, put package-lock=false and optionally save-exact=true in your project's .npmrc file. Compare whether you prefer the ergonomics of yarn global add over npm install -g or see fewer meaningless warnings for the specific set of dependencies you leverage.

3 upvotes·57.5K views
Lead Developer at Chore Champion·

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).

11 upvotes·1 comment·170.4K views
Damian Esteban
Damian Esteban
February 15th 2020 at 1:04AM

We recently made the switch to Yarn mostly because of workspaces, speed, and the features in the Yarn v2 release. It has been great.

View all (14)
Avatar of Tor Hagemann

Tor Hagemann

Principal Software Engineer at Socotra