[rushd][WS4] CLI client & command surface
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- nodejs, typescript
- 领域
- build-system, cli, devtools, tooling
调研方向
Start by reading the dependent issues #5896, #5897, and #5898, then examine the rush-client-core and rush-cli-client package entry points plus the existing rush and rushx commands. Verify the rush.json daemon block, routing precedence, daemon subcommands, graph protocol, and standalone rushx behavior against the listed acceptance criteria. Done means opt-in client behavior, validated configuration, correct streaming and exit handling, gated graph commands, and green CI tests.
由索引模型根据 Issue 内容生成。
描述
Build the separate CLI client package/bin (@rushstack/rush-cli-client on @rushstack/rush-client-core) and its command surface — fallback/opt-in routing, rush daemon subcommands, the rush.json daemon config block + env overrides, an experimental rush daemon graph reference client, and a standalone rushx-equivalent bin — all opt-in until cutover.
Depends on: #5896; #5897; #5898
Scope
rush-client-core+rush-cli-clientbin. Connect/forward/pump, the request envelope (argv,cwd,env,columns,colorLevel), stream pumping, exit-code relay, and cancel-on-signal — with noSIGWINCHforwarding (the client owns width/resize).- Fallback/opt-in routing. Decide daemon vs in-process per invocation from
RUSH_DAEMON,--no-daemon,rush.jsonconfig, CI detection, and the never-daemonize list (routing to today's in-process path otherwise). rush.jsondaemon config. A validateddaemonblock (enabled,idleTimeoutSeconds,autoStart,watch,queueTimeoutSeconds, plus the WS3 warm-set knobs) withRUSH_DAEMON*env overrides.rush daemonsubcommands.start|stop|restart|status|logs(themselves never-daemonized);statussurfaces warm-set + lifecycle info (uptime, PID, reload tier, warm projects, memory) andlogsstreams the daemon log.- Experimental
rush daemon graph. BehindRUSH_DAEMON_EXPERIMENTAL=1,show/status/scope-in/scope-out/invalidate/watch/pause/resumeover the warm graph, serving as a reference "third client" that consumes only structured events. - Standalone
rushx-equivalent. Run the cwd project's package script with the same auto-start/forward behavior; it becomesrushxat cutover (WS5).
Acceptance criteria
- The client connects, sends the request envelope, pumps stdout/stderr/stdin, and relays the daemon's exit code; Ctrl+C cancels the request;
SIGWINCHis handled client-side and not forwarded; a samplerush buildvia the client is behaviorally equivalent to in-process (full matrix in WS5). - Each routing input (
RUSH_DAEMON,--no-daemon, config, CI, never-daemonize) selects the correct path with a documented precedence order; CI defaults to in-process (no auto-start) unless explicitly opted in. - The
rush.jsondaemonschema is published and validates the block (rejecting unknown/invalid values) with precedence env > config > default. - Each
rush daemonsubcommand acts against a running (or absent) daemon with correct exit codes;statusreports warm-set + lifecycle info andlogsstreams the daemon log (see WS5). - The experimental
rush daemon graphverbs operate over the warm graph via the protocol only (no rush-lib-internal calls), consume only the presentation-free event contract, and stay gated off unlessRUSH_DAEMON_EXPERIMENTAL=1. - The standalone
rushx-equivalent resolves the project by cwd, forwards with auto-start, and matches today'srushxoutput/exit code for a sample script. -
rush-client-corehas norush-libdependency and commits its API Extractor report; everything ships opt-in until cutover; tests green in CI.
Part of #5894.
- 主要语言
- TypeScript
- 星标
- 6.5k
- 派生
- 710
- 平均合并
- 1 天 21 小时
- 30 天内合并 PR
- 46
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/rushstack 的其他 Issue
-
[rush] Upgrade the pnpm-sync-lib dependency to 0.3.5.可能已有人在做 @martinnaj 于 6 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
microsoft/rushstack#5971 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
microsoft/rushstack#5902 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
microsoft/rushstack#5839 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
microsoft/rushstack#5683 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 48/100
维护者通常 1 天内回复
查看 microsoft/rushstack 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
Comfy-Org/ComfyUI_frontend#20346 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
decentralized-identity/didwebvh-ts#203 ·
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 2/5 1-3 小时 新手友好度 65/100
lingdojo/kana-dojo#31791 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
Telegram webhook: line breaks lost since switch to rich messages可能已有人在做 @Kshot3000 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
github_actions security
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复