Environment
@clack/prompts 1.7.0 (also reproduced against current main rendering logic)- Node 22, macOS,
TERM=xterm-256color, 80-col PTY + xterm-headless grid
- CJK input used in the example, but the shift happens with ASCII input too (any text prompt value)
Minimal repro
import * as clack from '@clack/prompts'
clack.updateSettings({ withGuide: false })
await clack.text({ message: '插件包名' }) // type 测, then press EnterObserved
While the prompt is active, the input row is rendered flush-left:
◆ 插件包名
测█ ← cursor block right after the text, column 0 + displayWidth
After pressing Enter, the submitted (final) frame re-renders the value line with a 2-space indent:
◇ 插件包名
测 ← shifted right by 2 columns
So with withGuide: false, every text submit makes the content visibly jump 2 columns to the right.
With the default withGuide: true, both renderings carry the same │ prefix (3 columns), so the frames are consistent — the inconsistency only appears when the guide is turned off, because the submit branch keeps a 2-space indent (the leftover of the old │ prefix) while userInputWithCursor renders flush-left.
Byte streams (PTY capture, 80 cols)
Last redraw while typing 测 (active state, flush-left):
\x1b[999D\x1b[3A\x1b[1B\x1b[2K\x1b[G测█\x1b[2B
Full output after Enter (submit frame, 2-space-indented value line):
\x1b[999D\x1b[3A\x1b[J\x1b[32m◇\x1b[39m 插件包名\r\n \x1b[2m测\x1b[22m\r\n\x1b[?25h
The before the dimmed value in the submit frame is the discrepancy: no such prefix exists in the active render.
Expected
Under withGuide: false, the submitted value line should be rendered flush-left like the active input row (i.e. no 2-space carry-over), so the frame doesn't shift on submit.
Notes
Found while building a PTY-based CJK cursor regression harness; happy to send a PR if the fix direction (skip the 2-space indent on the submit branch when settings.withGuide === false) sounds right.
Environment
@clack/prompts1.7.0 (also reproduced against currentmainrendering logic)TERM=xterm-256color, 80-col PTY + xterm-headless gridMinimal repro
Observed
While the prompt is active, the input row is rendered flush-left:
After pressing Enter, the submitted (final) frame re-renders the value line with a 2-space indent:
So with
withGuide: false, every text submit makes the content visibly jump 2 columns to the right.With the default
withGuide: true, both renderings carry the same│prefix (3 columns), so the frames are consistent — the inconsistency only appears when the guide is turned off, because the submit branch keeps a 2-space indent (the leftover of the old│prefix) whileuserInputWithCursorrenders flush-left.Byte streams (PTY capture, 80 cols)
Last redraw while typing
测(active state, flush-left):Full output after Enter (submit frame, 2-space-indented value line):
The
Expected
Under
withGuide: false, the submitted value line should be rendered flush-left like the active input row (i.e. no 2-space carry-over), so the frame doesn't shift on submit.Notes
Found while building a PTY-based CJK cursor regression harness; happy to send a PR if the fix direction (skip the 2-space indent on the submit branch when
settings.withGuide === false) sounds right.