[rush reporter][R6] Add install-run-rush bootstrap handoff and compatibility adapters

Open
#5,979 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
nodejs, typescript
Domain
build-system, cli, tooling

Research direction

Start with the bootstrap and install-run-rush flow described here, then read RFC §5.5 to understand the handoff requirements. Trace how direct rush and bootstrap-mediated invocation select the frontend manager, and verify replay, deletion, truncation, overflow, permissions, cleanup, compatibility fallback, and legacy output behavior against the acceptance criteria.

Written by the indexing model from the issue text.

Description

enhancement

Parent: #5858

Blocked by: #5974, #5975

Goal

Extend reporter ownership to startup/version-selection output without destabilizing the existing bootstrap script.

Scope

  • Decide and implement the safest bootstrap shape: a reporter-aware install-run-rush variant, as suggested in #5858, or a backward-compatible prelude in the existing script.
  • Parse only early reporter controls in the zero-dependency bootstrap.
  • Buffer bounded Rush-owned startup envelopes, preserve inherited npm output as raw external output, and publish a nonce-protected handoff path via private environment variables.
  • Replay and delete the handoff in the frontend host; clean abandoned files.
  • Add new-frontend/old-engine and old-frontend/new-engine compatibility adapters with legacy-visible fallback.

Acceptance criteria

  • Direct rush and bootstrap-mediated invocation converge on one authoritative frontend manager.
  • Handoff replay/deletion, truncation, overflow, permissions, and cleanup behavior match RFC §5.5.
  • Unsupported explicit requests fail; automatic/implicit selection falls back safely.
  • Old global/new local and new global/old local combinations retain usable legacy output.
  • Existing bootstrap consumers are not forced onto the new visible reporter path.

DAG

Unblocks R9 and completes startup ownership; it is intentionally not on the shortest direct-invocation demo path.

Part of #5858.

Dominant language
TypeScript
Stars
6.5k
Forks
708
Avg merge
5d 7h
Merged PRs (30d)
44

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/rushstack

All issues in microsoft/rushstack

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.