Skip to content

Instantly share code, notes, and snippets.

@himalay
Created January 6, 2018 02:58
Show Gist options
  • Save himalay/2a68ddc662943d4c6321b7a0202c584c to your computer and use it in GitHub Desktop.
Save himalay/2a68ddc662943d4c6321b7a0202c584c to your computer and use it in GitHub Desktop.

npm vs yarn

What you need to know

npm install === yarn

Install is the default behavior.

npm install taco --save === yarn add taco

The Taco package is saved to your package.json immediately.

npm uninstall taco --save === yarn remove taco

--save can be defaulted in NPM by npm config set save true but this is non-obvious to most developers. Adding and removing from package.json is default in Yarn.

npm install taco --save-dev === yarn add taco --dev

npm update --save === yarn upgrade

Great call on upgrade vs update, since that is exactly what it is doing! Version number moves, upgrade is happening!

WARNING

npm update --save seems to be kinda broken in 3.11

npm install taco@latest --save === yarn add taco

npm install taco --global === yarn global add taco

As always, use global flag with care.

What you know about Yarn

npm init === yarn init

npm link === yarn link

npm outdated === yarn outdated

npm publish === yarn publish

npm run === yarn run

npm cache clean === yarn cache clean

npm test === yarn test

npm login === yarn login (and logout)

Things yarn has that NPM doesn’t

yarn licenses ls

Allows you to inspect the licenses of your dependencies

yarn licenses generate-disclaimer

Automatically create your license dependency disclaimer

yarn why taco

Identify why ‘taco’ package is installed, detailing which other packages depend upon it (thanks Olivier Combe).

Things NPM has that yarn doesn’t

npm xmas NO EQUIVALENT

npm visnup NO EQUIVALENT

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment