@microsoft/rush
Advanced tools
A professional solution for consolidating all your JavaScript projects in one Git repo
@microsoft/rush is a monorepo management tool designed to help developers manage large-scale projects with multiple packages. It provides a robust set of features for orchestrating builds, managing dependencies, and automating workflows in a monorepo setup.
Monorepo Management
Initializes a new Rush monorepo. This command sets up the necessary configuration files and directory structure to start managing multiple packages within a single repository.
rush initDependency Management
Updates the dependencies for all projects in the monorepo. This command ensures that all packages are using the correct versions of their dependencies as specified in the Rush configuration.
rush updateBuild Orchestration
Builds all projects in the correct order based on their dependency graph. This command ensures that each project is built only after its dependencies have been built.
rush buildChange Tracking
Generates change files based on the changes made to the projects. This is useful for maintaining a changelog and for versioning packages in a controlled manner.
rush changePublishing
Publishes the packages to a package registry. This command handles versioning and ensures that only the packages with changes are published.
rush publishLerna is a popular tool for managing JavaScript projects with multiple packages. It provides similar functionality to Rush, such as dependency management and build orchestration. However, Lerna is generally considered to be more lightweight and easier to set up, while Rush offers more advanced features and better performance for large-scale projects.
Nx is a set of extensible dev tools for monorepos, which helps you develop like Google, Facebook, and Microsoft. It offers powerful features for managing dependencies, building projects, and optimizing workflows. Compared to Rush, Nx provides a more integrated development experience with additional features like code generation and testing utilities.
Rush makes life easier for JavaScript developers who build and publish many NPM packages at once. If you're looking to consolidate all your projects into a single repo, you came to the right place! Rush is a fast, professional solution for managing this scenario. It gives you:
A single NPM install: In one step, Rush installs all the dependencies for all your projects into a common folder. This is not just a "package.json" file at the root of your repo (which might set you up to accidentally require() a sibling's dependencies). Instead, Rush uses symlinks to reconstruct an accurate "node_modules" folder for each project, without any of the limitations or glitches that seem to plague other approaches.
⏵ This algorithm supports the PNPM, NPM, and Yarn package managers.
Automatic local linking: Inside a Rush repo, all your projects are automatically symlinked to each other. When you make a change, you can see the downstream effects without publishing anything, and without any npm link headaches. If you don't want certain projects to get linked, that's supported, too.
Fast builds: Rush detects your dependency graph and builds your projects in the right order. If two packages don't directly depend on each other, Rush parallelizes their build as separate Node.js processes (and shows live console output in a readable order). In practice this multi-process approach can yield more significant speedups than all those async functions in your single-threaded Gulpfile.
Subset and incremental builds: If you only plan to work with a few projects from your repo, rush rebuild --to <project> does a clean build of just your upstream dependencies. After you make changes, rush rebuild --from <project> does a clean build of only the affected downstream projects. And if your toolchain is package-deps-hash enabled, rush build delivers a powerful cross-project incremental build (that also supports subset builds).
Cyclic dependencies: If you have hammers that build hammer-factory-factories, Rush has you covered! When a package indirectly depends on an older version of itself, projects in the cycle use the last published version, whereas other projects still get the latest bits.
Bulk publishing: When it's time to do a release, Rush can detect which packages have changes, automatically bump all the appropriate version numbers, and run npm publish in each folder. If you like, configure your server to automatically run rush publish every hour.
Changelog tracking: Whenever a PR is created, you can require developers to provide a major/minor/patch log entry for the affected projects. During publishing, these changes will be automatically aggregated into a nicely formatted CHANGELOG.md file.
Enterprise policies: Want to review new libraries before developers add them to package.json, but avoid hassling people about already approved cases? Want to enforce that all your projects depend on the same library version numbers? Are unprofessional personal e-mail addresses accidentally showing up in your company's Git history? Rush can help maintain a consistent ecosystem when you've got many developers and many projects in the mix.
Lots more! Rush was created by the platform team for Microsoft SharePoint. We build hundreds of production NPM packages every day, from internal and public Git repositories, for third party SDKs and live services with millions of users. If there's an important package management problem that needs solvin', it's likely to end up as a feature for Rush.
See Rush in action! From your shell, install the tool like this:
$ npm install -g @microsoft/rush
For command-line help, do this:
$ rush -h
To see Rush build some real projects, try running these commands: :-)
$ git clone https://github.com/microsoft/rushstack
$ cd rushstack
$ rush install
$ rush install # <-- instantaneous!
$ rush rebuild
$ rush build # <-- instantaneous!
(If you don't have a GitHub account set up, you can use rush install --bypass-policy.)
For more details and support resources, please visit: https://rushjs.io
Rush is part of the Rush Stack family of projects.
FAQs
A professional solution for consolidating all your JavaScript projects in one Git repo
The npm package @microsoft/rush receives a total of 598,093 weekly downloads. As such, @microsoft/rush popularity was classified as popular.
We found that @microsoft/rush demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Bybit's $1.46B hack by North Korea's Lazarus Group pushes 2025 crypto losses to $1.6B in just two months, already surpassing all of 2024's $1.49B total.
Security News
OpenSSF has published OSPS Baseline, an initiative designed to establish a minimum set of security-related best practices for open source software projects.
Security News
Michigan TypeScript founder Dimitri Mitropoulos implements WebAssembly runtime in TypeScript types, enabling Doom to run after processing 177 terabytes of type definitions.