rush update
Install package dependencies for all projects in the repo, and create or update the shrinkwrap file as needed
Options
| Name | Description |
|---|---|
-p, --purge | Perform "rush purge" before starting the installation |
--bypass-policy | Overrides enforcement of the "gitPolicy" rules from rush.json (use honorably!) |
--no-link | If "--no-link" is specified, then project symlinks will NOT be created after the installation completes. You will need to run "rush link" manually. This flag is useful for automated builds that want to report stages individually or perform extra operations in between the two stages. This flag is not supported when using workspaces |
--network-concurrency <COUNT> | If specified, limits the maximum number of concurrent network requests. This is useful when troubleshooting network failures |
--debug-package-manager | Activates verbose logging for the package manager. You will probably want to pipe the output of Rush to a file when using this command |
--max-install-attempts <NUMBER> | Overrides the default maximum number of install attempts. The default value is 3 |
--ignore-hooks | Skips execution of the "eventHooks" scripts defined in rush.json. Make sure you know what you are skipping |
--variant <VARIANT> | Run command using a variant installation configuration. This parameter may alternatively be specified via the RUSH_VARIANT environment variable |
--full | Normally "rush update" tries to preserve your existing installed versions and only makes the minimum updates needed to satisfy the package.json files. This conservative approach prevents your PR from getting involved with package updates that are unrelated to your work. Use "--full" when you really want to update all dependencies to the latest SemVer-compatible version. This should be done periodically by a person or robot whose role is to deal with potential upgrade regressions |
--recheck | If the shrinkwrap file appears to already satisfy the package.json files, then "rush update" will skip invoking the package manager at all. In certain situations this heuristic may be inaccurate. Use the "--recheck" flag to force the package manager to process the shrinkwrap file. This will also update your shrinkwrap file with Rush's fixups. (To minimize shrinkwrap churn, these fixups are normally performed only in the temporary folder.) |