This monorepo hosts code samples for the Rush Stack family of tools.
- What is Rush Stack? - learn about the mission behind these projects
- Zulip chat room - chat with the Rush Stack developers
- rushstack - the main monorepo where the Rush Stack tools are developed
- rush-example - a minimal Rush repo that demonstrates the fundamentals of Rush without relying on any other Rush Stack tooling
- rushstack-legacy - older projects that are still maintained but no longer actively developed
| Folder | Description |
|---|---|
| /heft/heft-fastify-tutorial | This project illustrates usage of Fastify with Heft |
| /heft/heft-node-basic-tutorial | This project illustrates a minimal tutorial Heft project targeting the Node.js runtime |
| /heft/heft-node-jest-tutorial | Illustrates how various Jest features work with Heft |
| /heft/heft-node-rig-tutorial | This project illustrates a minimal tutorial Heft project targeting the Node.js runtime and using a rig package |
| /heft/heft-storybook-react-tutorial | This project illustrates usage of Storybook with Heft |
| /heft/heft-storybook-react-tutorial-storykit | Storybook build dependencies for heft-storybook-react-tutorial |
| /heft/heft-webpack-basic-tutorial | This project illustrates a minimal tutorial Heft project targeting the web browser runtime |
| /other/packlets-tutorial | This project illustrates how to use @rushstack/eslint-plugin-packlets |
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 [email protected] with any additional questions or comments.