Improve this page

Environment variables

The Rush tool’s behavior can be customized using the shell environment variables described below:

If this variable is set to true, Rush will create symlinks with absolute paths instead of relative paths. This can be necessary when a repository is moved during a build or if parts of a repository are moved into a sandbox.


If this variable is set to true, Rush will not fail the build when running a version of Node that does not match the criteria specified in the nodeSupportedVersionRange field from rush.json.


This environment variable can be used to specify the --target-folder parameter for the rush deploy command.


Specifies the maximum number of concurrent processes to launch during a build. For more information, see the command-line help for the --parallelism parameter for rush build.


When using PNPM as the package manager, this variable can be used to configure the path that PNPM will use as the store directory.

If a relative path is used, then the store path will be resolved relative to the process’s current working directory. An absolute path is recommended.


This variable overrides the version of Rush that will be installed by the version selector. The default value is determined by the rushVersion field from rush.json.

For example, if you want to try out a different release of Rush before upgrading your repo, you can assign the variable like this:

$ set RUSH_PREVIEW_VERSION=5.0.0-dev.25
$ rush install


This variable overrides the temporary folder used by Rush. The default value is common/temp under the repository root.


This variable selects a specific installation variant for Rush to use when installing and linking package dependencies.

For more information about this feature, see Installation Variants.