Pressing Ctrl+C after vp run dev, pnpm run dev, or npm run dev leaves the terminal in a broken state on Windows

[Curtion]

Describe the bug

• On Windows, after starting the dev server and stopping it with Ctrl+C, the terminal is left in a broken or unusable state.

• Common symptoms include:

  • terminal input becomes sluggish or freezes
  • Backspace behaves incorrectly and prints ^H
  • Ctrl+C is echoed as ^C

• This issue is reproducible with vp run dev, pnpm run dev, and npm run dev.

• The issue does not reproduce with:

  • bun run dev
  • .\node_modules\.bin\vite.CMD
  • .\node_modules\.bin\vite.ps1
  • C:\Users\Curtion\Desktop\node-v24.14.1-win-x64\npm.cmd run dev(Native Node.js)
  • C:\Users\Curtion\Desktop\node-v24.14.1-win-x64\npm.ps1 run dev(Native Node.js)

PixPin_2026-03-28_12-59-32.mp4

Reproduction

https://github.com/Curtion/report-vite-plus-1

Steps to reproduce

• Open a terminal on Windows.
• Go to the project root directory.
• Run one of the following commands:
  • vp run dev
  • pnpm run dev
  • npm run dev
• Wait for the dev server to start.
• Press Ctrl+C once to stop the process.
• Observe that the terminal enters an abnormal state:
  • input becomes slow or unresponsive
  • Backspace prints ^H
  • Ctrl+C prints ^C

System Info

@Curtion ➜ report-vite-plus-1 git(main) vp env current
VITE+ - The Unified Toolchain for the Web

Environment:
  Version  24.14.1
  Source   lts

Tool Paths:
  node  C:\Users\Curtion\.vite-plus\js_runtime\node\24.14.1\node.exe
  npm   C:\Users\Curtion\.vite-plus\js_runtime\node\24.14.1\npm.cmd
  npx   C:\Users\Curtion\.vite-plus\js_runtime\node\24.14.1\npx.cmd
@Curtion ➜ report-vite-plus-1 git(main) vp --version  
VITE+ - The Unified Toolchain for the Web

vp v0.1.14

Local vite-plus:
  vite-plus  Not found

Tools:
  vite             Not found
  rolldown         Not found
  vitest           Not found
  oxfmt            Not found
  oxlint           Not found
  oxlint-tsgolint  Not found
  tsdown           Not found

Environment:
  Package manager  pnpm v10.28.0
  Node.js          v24.14.1
@Curtion ➜ report-vite-plus-1 git(main)

Used Package Manager

pnpm

Logs

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.

[fengmk2]

@Curtion Can you show me the vp env doctor result?

[Curtion]

@Curtion Can you show me the vp env doctor result?

@Curtion ➜ ~ vp env doctor 
VITE+ - The Unified Toolchain for the Web

Installation
  ✓ VITE_PLUS_HOME    C:\Users\Curtion\.vite-plus
  ✓ Bin directory     exists
  ✓ Shims             node, npm, npx, vpx

Configuration
  ✓ Shim mode         managed

PATH
  ✓ vp                first in PATH
  ✓ node              C:\Users\Curtion\.vite-plus\bin\node.exe (vp shim)
  ✓ npm               C:\Users\Curtion\.vite-plus\bin\npm.exe (vp shim)
  ✓ npx               C:\Users\Curtion\.vite-plus\bin\npx.exe (vp shim)
  ✓ vpx               C:\Users\Curtion\.vite-plus\bin\vpx.exe (vp shim)

Version Resolution
  Directory         C:\Users\Curtion
  Source            lts
  Version           24.14.1
  ✓ Node binary       installed

✓ All checks passed
@Curtion ➜ ~ 

[fengmk2]

I know what the problem is. Since your current project doesn't depend on vite-plus, vp run dev actually falls back to pnpm run dev, which caused this issue. Once #1179 this PR is merged, vp run dev will have the same effect as bun run dev.

[Curtion]

I know what the problem is. Since your current project doesn't depend on vite-plus, vp run dev actually falls back to pnpm run dev, which caused this issue. Once #1179 this PR is merged, vp run dev will have the same effect as bun run dev.

From my env, node, npm, npx are all vp shims. So pnpm run dev also goes through the shim — and it breaks too. Meanwhile native npm.ps1 run dev, bun run dev, and .\node_modules\.bin\vite.ps1 all work fine.

PR #1179 just changes the routing, but the task runner still spawns Node.js through the same shim, so I suspect the console corruption might still occur.

[fengmk2]

@Curtion I've released an alpha test version, could you help test it? Upgrade via vp upgrade --tag alpha, then run vp run dev to see if the issue still exists.

[Curtion]

@Curtion I've released an alpha test version, could you help test it? Upgrade via vp upgrade --tag alpha, then run vp run dev to see if the issue still exists.

I tested with v0.1.15-alpha.5 (vp upgrade --tag alpha), and the issue has been resolved. Thanks for the fix!