Which is Better Monorepo Management Toolset?
@microsoft/rush vs lerna

1 Year
@microsoft/rushlerna
What's Monorepo Management Toolset?

A monorepo is a place where many different projects are stored together, all managed using version control. Sometimes these projects are separate and managed by different teams. Some companies choose to keep all their source code in one public repository. Using a monorepo has advantages like making it easier to reuse code, manage dependencies, and collaborate with other teams. However, as the number of projects in the monorepo increases, it becomes important to manage it effectively. This is where a monorepo management toolset comes in. It includes various tools and practices that help developers work efficiently, maintain consistent code, and automate repetitive tasks in the monorepo.

NPM Package Downloads Trend
Github Stars Ranking
Stat Detail
Package
Weekly Downloads
Github Stars
Open Issues
Last Commit
License
lerna1,136,20435,3253542 days agoMIT License
@microsoft/rush845,9565,581816a day agoOther
Feature Comparison
Features@microsoft/rushlerna
Monorepo Management
@microsoft/rush is a toolkit for managing monorepos, with a focus on developer productivity and collaboration.
Lerna is a popular monorepo management tool that simplifies versioning, publishing, and project organization.
Build Optimization
@microsoft/rush provides tools for monorepo management but does not have specific build optimization features.
Lerna simplifies package versioning and publication but does not have built-in build optimization features.
Package Versioning
@microsoft/rush provides tools for managing package versioning and offers versioning policies for consistency.
Lerna is known for its versioning features, enabling consistent versioning and publication of packages within a monorepo.
Developer Productivity
@microsoft/rush aims to enhance developer productivity with tools for managing monorepos and package versioning.
Lerna simplifies package management but does not have specific developer productivity features.
Community
@microsoft/rush is backed by Microsoft and has a growing community with a focus on enterprise-level development.
Lerna has a well-established community and a wide ecosystem of plugins and extensions.
Integration with Other Tools
@microsoft/rush is designed to work with a range of development tools and can be adapted to fit different workflows.
Lerna is compatible with various development tools and workflows and can be integrated into existing setups.
NPM Package Introudction

@microsoft/rush

rush
      https://rushjs.io

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.

3 Minute Demo

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.)

Getting Started

For more details and support resources, please visit: https://rushjs.io

Links

Rush is part of the Rush Stack family of projects.