rnx-kit is a collection of MIT-licensed TypeScript tools built by Microsoft engineers for React Native developers who need to manage dependencies, bundle code, and build mobile apps consistently across large projects.

What it is

rnx-kit is a set of command-line and build tools for the React Native ecosystem, created by Microsoft engineers and maintained as open source under the MIT License. It ships as a set of individual tools that can be used one at a time or installed together through an "all in one" CLI, and it targets platforms including Android, iOS, macOS, desktop, and mobile development. The project's stated aim is to optimize the React Native developer experience and fill gaps in the surrounding tooling.

The concrete problems it addresses are dependency drift and bundler limitations in large codebases. In a big project, package versions can silently diverge between packages, which align-deps corrects by ensuring consistent dependency versions. Bundling with Metro, by default, does not validate TypeScript, prune dead code, or report problematic dependency graphs, and heavy native toolchains must usually be installed locally to produce Android and iOS binaries. rnx-kit addresses each of these through specific tools rather than a single monolithic framework.

Key capabilities

• align-deps manages and aligns dependency versions across large multi-package projects.
• metro-serializer extends Metro to add TypeScript validation during bundling.
• The same Metro extension enables tree shaking to remove unused code.
• metro-serializer detects duplicate dependencies and cyclic dependencies in the bundle graph.
• build builds Android and iOS apps in the cloud, marked experimental, avoiding local installation of heavy native toolchains.
• A Babel preset for Metro provides opinionated defaults tailored to Microsoft usage.
• An "all in one" CLI installs and exposes most of the tools for a project at once.

Who uses it and how

• Teams shipping React Native apps at scale, since the README states the tools are used every day to ship apps across Microsoft.
• Large multi-package repositories where dependency versions must stay consistent, using align-deps as part of the workflow.
• Projects that want to run TypeScript checks and tree shaking inside the Metro bundling step rather than in a separate pass.
• Teams that prefer not to install Android and iOS toolchains on developer machines, using the cloud-based build command instead.
• Individual developers evaluating a single tool in isolation, since each tool has its own README in the documentation's Tools section.

Getting started

The documentation website's Introduction guide walks through adding the "all in one" CLI to a project, while the Getting started guide covers adopting align-deps on its own; individual tools are documented separately in the Tools section.

How it compares

rnx-kit does not present itself as a replacement for a competing React Native toolkit; instead it fills specific gaps in the React Native tooling ecosystem around dependency alignment, Metro bundling, and cloud builds. Its Metro-related additions build on top of Metro itself rather than replacing it, so it composes with an existing React Native setup instead of requiring a migration.

When to use it — and when not

A team adopting it should note that the native cloud build tool is explicitly marked experimental, so it is better suited to experimentation or non-critical pipelines than to a hard release dependency. Developers who need nothing beyond stock React Native bundling, or who require a tool with a different licence or ownership model, should evaluate alternatives, and the Microsoft-tailored Babel defaults may not match every team's conventions. The README is relatively brief and points readers to the documentation site for detail, so the depth of each tool's capabilities is best assessed there before committing.