4 Commits

Author	SHA1	Message	Date
claude-code-best	6182015005	style: 完成所有文件的lint	2026-05-01 21:39:30 +08:00
claude-code-best	e38d45460e	fix: 修复 Windows Node.js 构建产物因 stdin.ref() 泄漏导致进程挂起 (#353) ... startCapturingEarlyInput() 调用 stdin.ref() 后，如果 Ink 未能接管 （如 raw mode 不支持或 setup 阶段异常），unref() 永远不会被调用， 导致 Node.js 事件循环无法退出。修复包括： - stopCapturingEarlyInput() 中补充 stdin.unref() 调用 - 新增 10s 安全阀定时器自动清理 leaked ref() - Ink App.componentWillUnmount 兜底 unref() 非 TTY stdin Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>	2026-04-24 21:16:15 +08:00
guunergooner	4b44047931	fix: prevent iTerm2 terminal response sequences from leaking into REPL input (#172) ... The earlyInput capture's escape sequence detection was too simplistic — it only checked if the byte after ESC fell in 0x40-0x7E range, treating it as a terminator. This caused DCS sequences (e.g. XTVERSION `\x1bP>|iTerm2 3.6.4\x1b\\`) and CSI parameter sequences (e.g. DA1 `\x1b[?64;...c`) to partially leak into the input buffer as `>|iTerm2 3.6.4?64;1;2;4;6;17;18;21;22c`. Fix by handling each escape sequence type per ECMA-48: - CSI (`ESC [`): skip parameter + intermediate bytes, then final byte - DCS/OSC/SOS/PM (`ESC P/]/X/^`): scan to BEL or ST terminator - Other: keep single-byte skip Closes #171 Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>	2026-04-07 15:11:06 +08:00
claude-code-best	f90eee85d8	feat: build	2026-03-31 19:22:47 +08:00