|
The home for various projects maintained by the Rush Stack community, whose mission is to develop reusable tooling for large scale TypeScript monorepos.
- What is Rush Stack? - learn about the mission behind these projects
- API reference - browse API documentation for NPM packages
- Gitter chat room - chat with the Rush Stack developers
- Rush - a build orchestrator for large scale TypeScript monorepos
- API Extractor - create .d.ts rollups and track your TypeScript API signatures
- API Documenter - use TSDoc comments to publish an API documentation website
| Folder | Description |
|---|---|
| /build-tests/api-documenter-test | Building this project is a regression test for api-documenter |
| /build-tests/api-extractor-lib1-test | Building this project is a regression test for api-extractor |
| /build-tests/api-extractor-lib2-test | Building this project is a regression test for api-extractor |
| /build-tests/api-extractor-lib3-test | Building this project is a regression test for api-extractor |
| /build-tests/api-extractor-scenarios | Building this project is a regression test for api-extractor |
| /build-tests/api-extractor-test-01 | Building this project is a regression test for api-extractor |
| /build-tests/api-extractor-test-02 | Building this project is a regression test for api-extractor |
| /build-tests/api-extractor-test-03 | Building this project is a regression test for api-extractor |
| /build-tests/api-extractor-test-04 | Building this project is a regression test for api-extractor |
| /build-tests/heft-action-plugin | This project contains a Heft plugin that adds a custom action |
| /build-tests/heft-action-plugin-test | This project exercises a custom Heft action |
| /build-tests/heft-example-plugin-01 | This is an example heft plugin that exposes hooks for other plugins |
| /build-tests/heft-example-plugin-02 | This is an example heft plugin that taps the hooks exposed from heft-example-plugin-01 |
| /build-tests/heft-minimal-rig-test | This is a minimal rig package that is imported by the 'heft-minimal-rig-usage-test' project |
| /build-tests/heft-minimal-rig-usage-test | A test project for Heft that resolves its compiler from the 'heft-minimal-rig-test' package |
| /build-tests/heft-node-everything-test | Building this project tests every task and config file for Heft when targeting the Node.js runtime |
| /build-tests/heft-oldest-compiler-test | Building this project tests Heft with the oldest supported TypeScript compiler version |
| /build-tests/heft-rsc-test | Building this project tests Heft using the rush-stack-compiler rig package |
| /build-tests/heft-web-rig-library-test | A test project for Heft that exercises the '@rushstack/heft-web-rig' package |
| /build-tests/heft-webpack-everything-test | Building this project tests every task and config file for Heft when targeting the web browser runtime |
| /build-tests/localization-plugin-test-01 | Building this project exercises @microsoft/localization-plugin. This tests that the plugin works correctly without any localized resources. |
| /build-tests/localization-plugin-test-02 | Building this project exercises @microsoft/localization-plugin. This tests that the loader works correctly with the exportAsDefault option unset. |
| /build-tests/localization-plugin-test-03 | Building this project exercises @microsoft/localization-plugin. This tests that the plugin works correctly with the exportAsDefault option set to true. |
| /build-tests/node-library-build-eslint-test | |
| /build-tests/node-library-build-tslint-test | |
| /build-tests/rush-stack-compiler-2.4-library-test | |
| /build-tests/rush-stack-compiler-2.7-library-test | |
| /build-tests/rush-stack-compiler-2.8-library-test | |
| /build-tests/rush-stack-compiler-2.9-library-test | |
| /build-tests/rush-stack-compiler-3.0-library-test | |
| /build-tests/rush-stack-compiler-3.1-library-test | |
| /build-tests/rush-stack-compiler-3.2-library-test | |
| /build-tests/rush-stack-compiler-3.3-library-test | |
| /build-tests/rush-stack-compiler-3.4-library-test | |
| /build-tests/rush-stack-compiler-3.5-library-test | |
| /build-tests/rush-stack-compiler-3.6-library-test | |
| /build-tests/rush-stack-compiler-3.7-library-test | |
| /build-tests/rush-stack-compiler-3.8-library-test | |
| /build-tests/rush-stack-compiler-3.9-library-test | |
| /build-tests/ts-command-line-test | Building this project is a regression test for ts-command-line |
| /build-tests/web-library-build-test | |
| /heft-plugins/pre-compile-hardlink-or-copy-plugin | Heft plugin that can be used to create a hardlink before the compilation runs. |
| /libraries/rushell | Execute shell commands using a consistent syntax on every platform |
| /repo-scripts/doc-plugin-rush-stack | API Documenter plugin used with the rushstack.io website |
| /repo-scripts/generate-api-docs | Used to generate API docs for the rushstack.io website |
| /repo-scripts/repo-toolbox | Used to execute various operations specific to this repo |
| /stack/rush-stack-compiler-shared | |
| /tutorials/heft-node-basic-tutorial | This project illustrates a minimal tutorial Heft project targeting the Node.js runtime |
| /tutorials/heft-node-jest-tutorial | Building this project validates that various Jest features work correctly with Heft |
| /tutorials/heft-node-rig-tutorial | This project illustrates a minimal tutorial Heft project targeting the Node.js runtime and using a rig package |
| /tutorials/heft-webpack-basic-tutorial | This project illustrates a minimal tutorial Heft project targeting the web browser runtime |
This repo welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This repo 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.