Quick Start
This guide walks you from zero to a working project in a few commands.
1. Create a new project
Section titled “1. Create a new project”If you already have a package.json, skip to step 2.
Create a minimal package.json by hand or with npm:
mkdir my-app && cd my-appnpm init -y2. Install dependencies
Section titled “2. Install dependencies”rush installRush reads your package.json, resolves the full dependency tree, downloads and extracts every package into node_modules/, and writes a rush.lock file to pin exact versions.
3. Add a package
Section titled “3. Add a package”rush add expressrush add typescript --save-devThis updates package.json, resolves the new graph, and re-installs.
4. Run a script
Section titled “4. Run a script”rush run buildRush executes the build script from your package.json, automatically running prebuild and postbuild hooks if they exist.
5. Check for updates
Section titled “5. Check for updates”rush outdatedDisplays a colour-coded table of packages where newer versions are available.
What just happened?
Section titled “What just happened?”After rush install, your project directory looks like this:
my-app/├── node_modules/│ ├── .bin/ ← symlinked executables from direct deps│ ├── .rush/ ← content-addressed package store│ └── express/├── package.json└── rush.lock ← exact pinned versions — commit thisRush uses a content-addressed store inside node_modules/.rush/. Each package is extracted once and reused across installs via integrity sentinels, so subsequent rush install runs are nearly instant.
Useful commands
Section titled “Useful commands”| Command | What it does |
|---|---|
rush list | Show installed packages as a tree |
rush why <pkg> | Explain why a package is in your tree |
rush exec <bin> | Run a binary from node_modules/.bin |
rush trust add <pkg> | Allow a package to run install scripts |
Next: rush install →