モノレポ管理ツールは、複数のパッケージを単一のリポジトリで管理するためのツールです。これにより、依存関係の管理やビルドプロセスの最適化が容易になり、開発チームは効率的に作業を進めることができます。これらのツールは、特に大規模なプロジェクトや複数の関連するパッケージを持つプロジェクトにおいて、開発フローを改善するために使用されます。
Rushは、複数のパッケージ間の依存関係を厳密に管理し、バージョンの整合性を保つための機能を提供します。これにより、異なるパッケージ間での互換性を確保し、開発者が安心して作業できる環境を整えます。
Lernaは、パッケージのバージョンを一元管理し、依存関係の解決を簡素化します。特に、パッケージを個別に公開する際に便利です。
Nxは、依存関係グラフを可視化し、パッケージ間の依存関係を効率的に管理します。これにより、ビルドやテストの実行を最適化できます。
Turboは、依存関係の変更を検知し、必要な部分のみを再ビルドすることで、ビルド時間を大幅に短縮します。
Rushは、特に大規模なモノレポに最適で、依存関係の管理やビルドの最適化を重視しています。複雑なプロジェクトでのスケーラビリティが求められる場合に選択すべきです。
Lernaは、シンプルなモノレポ管理を提供し、パッケージのバージョン管理や公開を容易にします。小規模から中規模のプロジェクトに適しており、迅速なセットアップが可能です。
Nxは、モノレポの構築に特化したツールで、特にAngularやReactなどのフレームワークとの統合が強力です。アプリケーションのスケーラビリティと再利用性を重視する場合に選ぶべきです。
Turboは、ビルドプロセスの高速化に特化しており、特にCI/CDパイプラインでの効率を重視します。ビルド時間を短縮したい場合に最適です。
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.