Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[rush reporter][R9] Complete Rush 6 reporter and plugin migration

未关闭
#5,982 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
nodejs, typescript

调研方向

Start with parent issue #5858 and the blocked issues #5977, #5979, #5980, and #5981, then review the Rush reporter and rushd cutover described here. Done means the acceptance criteria pass: compatibility is tested before plugin execution, both Rush 5 and Rush 6 behavior are covered, the legacy fallback remains documented and tested, and the default flip is reversible.

由索引模型根据 Issue 内容生成。

描述

enhancement

Parent: #5858

Blocked by: #5977, #5979, #5980, #5981; coordinated with #5900

Goal

Execute the daemon-aligned Rush 6 reporter cutover after the opt-in path and compatibility gates are proven.

Scope

  • Deprecate and remove ILogger.terminal and RushSession.terminalProvider in the major release.
  • Gate incompatible plugins before apply() with the structured migration diagnostic.
  • Retain the legacy renderer, AlreadyReportedError bridge, verbosity aliases, and RUSH_REPORTER=legacy emergency fallback for at least one major.
  • Enable default reporter selection and environment-based agent selection in coordination with the rushd client/default flip.
  • Validate daemon and in-process clients consume the same presentation-free event stream and derive the same exit behavior.

Acceptance criteria

  • Plugin incompatibility is detected before plugin code executes.
  • Rush 5 compatibility behavior and Rush 6 breaking behavior are explicitly tested.
  • Reporter and rushd cutovers ship in the same major and pass #5900 transparency gates.
  • The legacy emergency path remains documented, tested, and independent of the daemon fallback.
  • Default flip is reversible to the opt-in behavior without protocol rollback.

DAG

Unblocks R11.

Part of #5858.

主要语言
TypeScript
星标
6.5k
派生
710
平均合并
1 天 21 小时
30 天内合并 PR
46

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

microsoft/rushstack 的其他 Issue

查看 microsoft/rushstack 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。