npm registry and can work alongside
npm, but it’s aim it to be a safer, more secure and more reliable alternative.
You can replace your whole
npm workflow with Yarn for new or current projects with very minimal effort. Dependencies in Yarn are kept in a
yarn.lock file that should be checked-in your source control, but the file itself is for Yarn only and shouldn’t be edited. Here just enough to get your started with Yarn.
There are a few ways to install Yarn. You can, ironically enough, install it through
npm install -g yarn
If you don’t have
npm installed, you can also install with a simple bash script:
curl -o- -L https://yarnpkg.com/install.sh | bash
On Windows, you can get an installer file here.
Run this to see if Yarn was properly installed or to see if you have the latest version:
To initialize a new project, run
Here’s how to install all the dependencies from your package.json file (the equivalent of
lodash for most of our examples:
add command to add a dependency to your project:
yarn add lodash
You will see an output like this:
Outputyarn add v1.22.5 info No lockfile found. [1/4] 🔍 Resolving packages... [2/4] 🚚 Fetching packages... [3/4] 🔗 Linking dependencies... [4/4] 🔨 Building fresh packages... success Saved lockfile. success Saved 1 new dependency. info Direct dependencies └─ email@example.com info All dependencies └─ firstname.lastname@example.org ✨ Done in 1.48s.
--dev (or its alias
-D) flag to add a package as a dev dependency:
yarn add babel-cli -D
yarn upgrade lodash
or upgrade all the dependencies:
yarn remove lodash
yarn global add lodash
This is a basic introduction to the Yarn Package Manager. Here are some other common commands:
yarn info lodash
yarn why lodash
yarn run test
Have fun with Yarn!
If you’ve enjoyed this tutorial and our broader community, consider checking out our DigitalOcean products which can also help you achieve your development goals.