`vp migrate` shows no progress for 3+ minutes after config merge steps

[kazupon]

Describe the bug

vp migrate takes over 3 minutes on a medium-sized project (~1625 packages in node_modules). After the following log output, the terminal appears to hang with no spinner or progress indication:

 Installing dependencies (2s)
✔ Created vite.config.ts in vite.config.ts
✔ Merged .oxlintrc.json into vite.config.ts
✔ Merged staged config into vite.config.ts

After these three messages, there is no spinner, no log output, and no indication of what is happening for 3+ minutes. This makes it look like the process is frozen.

the below reproduction video, which is recorded by screen studio (24x):

vp-migrate-issue.mp4

Reproduction

My private repo (Any medium-to-large project with ~30+ dependencies. The issue is more noticeable with more packages)

Steps to reproduce

1. Have a project with vite, vitest, eslint, and lint-staged configured
2. Run vp migrate
3. Answer the interactive prompts
4. After "Merged staged config into vite.config.ts", observe the terminal — no output for 3+ minutes

System Info

vp v0.1.14

Local vite-plus:
  vite-plus  v0.1.14

Tools:
  vite             v8.0.2
  rolldown         v1.0.0-rc.11
  vitest           v4.1.1
  oxfmt            v0.42.0
  oxlint           v1.57.0
  oxlint-tsgolint  v0.17.3
  tsdown           v0.21.4

Environment:
  Package manager  pnpm v10.33.0
  Node.js          v24.14.1

Used Package Manager

pnpm

Logs

No debug logs available — `vp migrate` does not support `--debug` or `--verbose` flags. `VITE_LOG=debug` only affects the Rust binary tracing and does not provide visibility into the JS migration steps.

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.

[kazupon]

I instrumented executeMigrationPlan() in the bundled migrate.js to measure each step. Tested on a monorepo project (~1625 packages in node_modules, 307 files with imports rewritten).

Used VITE_PLUS_FORCE_MIGRATE=1 vp migrate --no-interactive to force the full migration path.

I found out Rewrite configs (rewriteStandaloneProject / rewriteMonorepo) accounts for ~92% of total migration time.

In my monorepo project, rewriteStandaloneProject() / rewriteMonorepo() calls several sub-functions including rewriteAllImports(), which walks all TS/JS files via find_ts_files() and rewrites imports using ast-grep.
For 307 files, this averages ~0.6s per file.

This step runs with silent: true and no spinner update within the step, so the user sees no progress for over 3 minutes.

[kazupon]

@fengmk2
I've just invited to my project.
you can reproduce this issue.

[fengmk2]

@kazupon Thank you, I will follow up tomorrow. There should be a way to fix the performance issue, and the number of files doesn't seem too many.

[kazupon]

@fengmk2
I've just pinned to repro/1156 branch for reproduction.