CodeVetter · Repo Unpack · System map
microsoft/rushstack
The repository packages several developer tools around shared command-line, filesystem, build, and configuration infrastructure. Rush owns cross-project orchestration, while Heft supplies configurable execution within projects. API analysis, documentation, browser interfaces, daemon IPC, and MCP each have separate runtime boundaries. The inspected manifests and CI define package builds and integration checks; this map is bounded rather than exhaustive.
- README describes reusable tooling for large TypeScript monorepos and identifies Rush, Heft, API Extractor, API Documenter, and Lockfile Explorer as distinct products.
- rush.json pins Rush 5.179.0 and PNPM 10.27.0, specifies supported Node ranges, and constrains project folders to exactly two levels.
- Rush’s executable checks Node compatibility, discovers MinimalRushConfiguration, selects RUSH_PREVIEW_VERSION or the repository’s Rush version, and passes launch options to launchRushFrontendAsync.
- Heft initializes project configuration and InternalHeftSession before registering clean, run, per-phase, watch, and alias actions; its package exposes both CommonJS and ESM library outputs.
- API Extractor exposes a CLI and library API with rollup declarations; API Documenter consumes its JSON models through a separate CLI and library package.
- Lockfile Explorer runs Express on port 8091 and serves a packaged React application; its Heft build copies frontend assets and shared graph declarations/JavaScript from the private web package.
- Daemon transport uses POSIX sockets and PID JSON records under /tmp/rushd-<uid> or an absolute RUSHD_RUNTIME_DIR override; Windows uses named pipes and temporary-directory lockfiles.
- Packages commonly build/test through Heft and pack through rush-pnpm; CI installs dependencies, runs production retest, checks package-manager integration, and exercises source-built Rush against a second checkout.