Both npm and Yarn are used package.json
to track project dependencies, and while they have similar patterns and functionality, Yarn is not a fork, it addresses some of npm's shortcomings.
above sea level
Yarn
npm install
yarn install
(N/A)
yarn install --flat
(N/A)
yarn install --har
(N/A)
yarn install --no-lockfile
(N/A)
yarn install --pure-lockfile
npm install [package]
(N/A)
npm install --save [package]
yarn add [package]
npm install --save-dev [package]
yarn add [package] [--dev/-D]
(N/A)
yarn add [package] [--peer/-P]
npm install --save-optional [package]
yarn add [package] [--optional/-O]
npm install --save-exact [package]
yarn add [package] [--exact/-E]
(N/A)
yarn add [package] [--tilde/-T]
npm install --global [package]
yarn global add [package]
npm rebuild
yarn install --force
npm uninstall [package]
(N/A)
npm uninstall --save [package]
yarn remove [package]
npm uninstall --save-dev [package]
yarn remove [package]
npm uninstall --save-optional [package]
yarn remove [package]
npm cache clean
yarn cache clean
rm -rf node_modules && npm install
yarn upgrade
above sea level
Yarn
npm install
yarn install
(N/A)
yarn install --flat
(N/A)
yarn install --har
(N/A)
yarn install --no-lockfile
(N/A)
yarn install --pure-lockfile
npm install [package]
(N/A)
npm install --save [package]
yarn add [package]
npm install --save-dev [package]
yarn add [package] [--dev/-D]
(N/A)
yarn add [package] [--peer/-P]
npm install --save-optional [package]
yarn add [package] [--optional/-O]
npm install --save-exact [package]
yarn add [package] [--exact/-E]
(N/A)
yarn add [package] [--tilde/-T]
npm install --global [package]
yarn global add [package]
npm rebuild
yarn install --force
npm uninstall [package]
(N/A)
npm uninstall --save [package]
yarn remove [package]
npm uninstall --save-dev [package]
yarn remove [package]
npm uninstall --save-optional [package]
yarn remove [package]
npm cache clean
yarn cache clean
rm -rf node_modules && npm install
yarn upgrade