Okay, so you’ve heard about this new javascript package manager called yarn , installed it with npm i -g yarn , and now you want to know how to use it? For the most part if you know NPM, you’re already set! Here are the key notes for switching.
:+1: Feel free to bookmark this article, as it will update often as yarn grows.
Cheat Sheet ― What you need toknow npm install === yarn Install is the default behavior. npm install taco --save === yarn add taco The Taco package is saved to your package.json is 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 taco --save === yarn upgrade taco Great call on upgrade vs update, since that is exactly what it is doing! Version number moves, upgrade is happening! npm install taco --global === yarn global add taco As always, use global flag with care. What you already know aboutyarn 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 login === yarn login (and logout) npm test === yarn test Things yarn has that NPMdoesn’t
I’m skipping the items that they warn against using like yarn clean
yarn licenses ― Allows you to inspect the licenses of your dependencies yarn licenses generate ― Automatically create your license dependency disclaimer :arrow_up: Emojis Speed :runner: Automatic shrinkwrap with the yarn lockfile Security-centric design Things NPM has that yarndoesn’t npm xmas === **NO EQUIVALENT** npm visnup === **NO EQUIVALENT**Yarn’s run command seems to be kind of broken at the time of this writing. Looks like it will be fixed in 0.15.2 NPM has that over yarn, for now. Thanks for researching this Zachary !
MOAR! Yarn spools worthreading: