Installing the latest SemVer-compatible version of everything
rush update only makes the minimal incremental changes necessary to satisfy the the project package.json files. If you want to update everything to the latest version, you would do this:
# This effectively deletes the old shrinkwrap file and re-solves everything # using the latest compatible versions as specified in package.json files. # Note that the package.json files themselves are not modified. $ rush update --full
For everyday work,
--full can introduce unrelated breaks in your PR branch, for example if one of the dependencies didn’t perfectly follow the SemVer rules. This isn’t too much of a concern for small repos. For a large monorepo, we recommended to use
rush update for everyday work, and then run
rush update --full periodically as a separate workflow by a CI job or designated person.
Faster ways to build
If you’re only working on a few projects: Let’s say your Git repo contains 50 projects, but you really only work on the widget and widget-demo projects. You can ask Rush to build only those two projects, plus the libraries that they depend on:
rush rebuild --to widget --to widget-demo
If you changed a library: Let’s say your Git repo contains 50 projects, and you just fixed some bugs in the widget library. You need to run unit tests for all the projects that use this library, and anything that depends on them, but it would be wasteful to rebuild everything else. To rebuild just the downstream projects:
rush rebuild --from widget
The full set of project selection parameters are described in the article Selecting subsets of projects.
A faster way to install
If your repo is using PNPM with the new
useWorkspaces=true mode enabled in your rush.json file, you can use a feature called “filtered installs”. This feature reduces installation times by only installing the subset of NPM packages required to build a specific project.
# Only install the NPM packages needed to build "my-project" and the other # Rush projects that it depends on: $ rush install --to my-project # Like with "rush build", you can use "." to refer to the project from your # shell's current working directory: $ cd my-project $ rush install --to . # Here's how to install dependencies required to do "rush build --from my-project" $ rush install --from my-project
Getting back to a clean state
After working with Rush, maybe you want to get back to a clean state, e.g. so you can zip up a folder. Here’s a couple commands to do that:
# Remove all the symlinks created by Rush: $ rush unlink # Remove all the temporary files created by Rush, including deleting all # the NPM packages that were installed in your common folder: $ rush purge