Important: This documentation covers Yarn 2. For the 1.x doc, check
yarn addyarn binyarn cache cleanyarn config getyarn config setyarn configyarn constraints queryyarn constraints sourceyarn constraintsyarn dlxyarn inityarn installyarn linkyarn nodeyarn npm infoyarn npm loginyarn npm publishyarn npm whoamiyarn packyarn patch-commityarn patchyarn plugin importyarn plugin listyarn plugin runtimeyarn rebuildyarn removeyarn runyarn set resolutionyarn set version from sourcesyarn set versionyarn stageyarn unplugyarn upyarn upgrade-interactiveyarn version applyyarn version checkyarn versionyarn whyyarn workspaceyarn workspaces foreachyarn workspaces list

yarn stage

Add all yarn files to your vcs.


$> yarn stage [-c,--commit] [-r,--reset] [-u,--update] [-n,--dry-run]


Adds all modified project files to the staging area :

yarn stage

Creates a new commit containing all modified project files :

yarn stage --commit


This command will add to your staging area the files belonging to Yarn (typically any modified package.json and .yarnrc.yml files, but also linker-generated files, cache data, etc). It will take your ignore list into account, so the cache files won't be added if the cache is ignored in a .gitignore file (assuming you use Git).

Running --reset will instead remove them from the staging area (the changes will still be there, but won't be committed until you stage them back).

Since the staging area is a non-existent concept in Mercurial, Yarn will always create a new commit when running this command on Mercurial repositories. You can get this behavior when using Git by using the --commit flag which will directly create a commit.