Repository navigation
Spinner interrupt exit code differs between the Rust and TypeScript implementations #3429
Description
Vite+ has two spinner implementations, and they exit with different codes when the user interrupts them.
| Rust spinner | TypeScript spinner | |
|---|---|---|
| Location | crates/vp_shared/src/progress/input.rs |
packages/prompts/src/spinner.ts |
| Example commands | vp install -g, vp upgrade |
Interactive vp migrate, vp create |
| Ctrl+C | Ends by SIGINT, exit code 130 |
Exit code 0 |
SIGTERM |
Ends by SIGTERM, exit code 143 |
Keeps running, then exit code 0 |
The TypeScript spinner should match the Rust spinner, so that an interrupted command does not report success. For example, vp migrate && git commit currently continues to the commit after Ctrl+C.
Cause
block()from@clack/coreswitches stdin to raw mode and callsprocess.exit(0)when it receives Ctrl+C.- The spinner's
SIGINTandSIGTERMlisteners stop the spinner and return, so Node keeps the process running.
Metadata
Metadata
Assignees
Labels
Type
Fields
Priority
None yet
Start date
None yet
Target date
None yet
Effort
None yet
Activity
jong-kyung commentedon Nov 11, 2026
@fengmk2 Should we make the exit codes consistent here?
fengmk2 commentedon Nov 11, 2026
We need to standardize this, and also consider which exit code would be most appropriate.
jong-kyung commentedon Nov 11, 2026
I think we should match the Rust spinner. It lets the signal end the process, so the shell reports 130 for Ctrl+C and 143 for
SIGTERM.fix(prompts): end an interrupted spinner with the signal status (void…