stack/packages
Bilal Godil a9c22da3bd fix(cli): don't fall back when npx is killed by a signal; harden tests
Review follow-ups:
- A Ctrl-C forwarded to the npx child surfaced as exit code null (-> 1), which
  the fallback logic misread as an npx failure and relaunched dev on the
  installed CLI instead of aborting. Capture the terminating signal in
  runReexec and propagate (128+signum) instead of falling back.
- Scrub STACK_CLI_REEXEC_MARKER from the wrapped user command's env so the
  internal handshake var doesn't leak into arbitrary child processes.
- Add wiring tests (marker present -> propagate; absent -> fall back without
  process.exit) and a signal-abort case, so a regression in the glue between
  createReexecMarker/spawn/decidePostReexec is caught.
2026-06-16 14:46:58 -07:00
..
cli fix(cli): don't fall back when npx is killed by a signal; harden tests 2026-06-16 14:46:58 -07:00
dashboard-ui-components chore: update package versions 2026-06-16 19:32:53 +00:00
js chore: update package versions 2026-06-16 19:32:53 +00:00
next chore: update package versions 2026-06-16 19:32:53 +00:00
react chore: update package versions 2026-06-16 19:32:53 +00:00
sc chore: update package versions 2026-06-16 19:32:53 +00:00
shared chore: update package versions 2026-06-16 19:32:53 +00:00
shared-backend chore: update package versions 2026-06-16 19:32:53 +00:00
tanstack-start chore: update package versions 2026-06-16 19:32:53 +00:00
template chore: update package versions 2026-06-16 19:32:53 +00:00
ui chore: update package versions 2026-06-16 19:32:53 +00:00