Displays a table of packages that have newer versions available, colour-coded by update type.
Package Current Wanted Latest Type
─────────────────────────────────────────────────────────
express 4.17.3 4.18.2 4.18.2 dependencies
react 18.1.0 18.2.0 18.3.1 dependencies
typescript 4.9.5 4.9.5 5.3.3 devDependencies (dev)
lodash 3.10.1 3.10.1 4.17.21 dependencies
| Column | Description |
|---|
| Package | Package name. (dev), (optional), (peer) suffixes indicate non-regular deps. |
| Current | The version currently installed (from rush.lock). |
| Wanted | The highest version satisfying your declared range in package.json. |
| Latest | The dist-tags.latest from the registry — the most recent stable release regardless of your range. |
| Type | Which dependency field the package appears in. |
| Colour | Meaning |
|---|
| Green | Patch update (e.g. 4.18.1 → 4.18.2) — generally safe |
| Yellow | Minor update (e.g. 4.17.3 → 4.18.2) — check the changelog |
| Red | Major update (e.g. 3.10.1 → 4.17.21) — may include breaking changes |
| Dim | Already on the latest version |
rush outdated never modifies package.json or rush.lock. It’s a read-only check.- Registry fetches happen in parallel, so it’s fast even for large dependency trees.
- Packages that fail to fetch from the registry (e.g. private packages without auth) are silently skipped.
- To actually upgrade, edit your version ranges in
package.json and run rush install.