0f5a3f2873
|
||
|---|---|---|
| .ccache | ||
| .changeset | ||
| .github | ||
| .vscode | ||
| .yarn | ||
| docsite | ||
| incubator | ||
| packages | ||
| scripts | ||
| .clang-format | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .swiftformat | ||
| .yarnrc.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| ROADMAP.md | ||
| SECURITY.md | ||
| nx.json | ||
| package.json | ||
| yarn.lock | ||
README.md
rnx-kit - React Native tooling by and for developers
rnx-kit is a collection of battle-tested tools created by Microsoft engineers
to optimize the React Native developer experience. It helps filling gaps in the
React Native ecosystem and streamlines the developer workflow.
These tools are actively used every day to ship React Native apps at scale across Microsoft; now they're open source and available for any React Native project.
What's included
rnx-kit includes tools for:
- Dependency management - Ensure consistent dependency versions across large
projects with
align-deps. - Native builds (experimental) - Build Android and iOS apps in the cloud with
build. Avoid installing heavy native toolchains. - Better bundling -
metro-serializerallows the enhancement of Metro to add features such as TypeScript validation with Metro, tree shaking, duplicate and cyclic dependencies detection. - Microsoft-tailored defaults - you can find Babel preset for Metro opinionated for Microsoft usage.
And many more!
Get started
Please follow Introduction guide on the documentation website to learn about how you can quickly add the "all in one" CLI to your project and get most of the tools set out of the box.
Or follow the Getting started guide for an easy introduction to our dependency management tool.
If you want to use only a specific tool, you can refer to its `README`` for details; they are all easily readable in the Tools section of the documentation.
Contributing
rnx-kit is built for the community, by the community - and maintained by
Microsoft engineers. Your contributions are welcome!
Take a look at CONTRIBUTING for details.
If you are interested in proposing "substantial" changes, please refer to our RFC process.
License
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.