vp check --fix stuck

[Zoomelectrico]

Describe the bug

Here's the translated GitHub issue text:

---

4 days ago I created a new project using the @tanstack/start CLI.
Today I decided to run pnpm up --latest to update my dependencies.
Everything is working fine, however, when I try to commit, the hooks get stuck trying to run vp check --fix.

I have run the command vp check --fix on its own with the --no-lint and --no-fmt flags, tried disabling typeAware: true and typeCheck: true in vite.config.ts.

Nothing has worked — I deleted pnpm-lock.yaml and node_modules and still can't get the check to work again.

My current versions:

vp --version
VITE+ - The Unified Toolchain for the Web
vp v0.1.24
Local vite-plus:
  vite-plus  v0.1.23
Tools:
  vite             v8.0.14
  rolldown         v1.0.3
  vitest           v4.1.7
  oxfmt            v0.52.0
  oxlint           v1.67.0
  oxlint-tsgolint  v0.23.0
  tsdown           v0.22.0
Environment:
  Package manager  pnpm v11.3.0
  Node.js          v24.16.0

My machine:

MacBook Air
Apple M1
16GB RAM
MacOS 26.5 (25F71)

Reproduction

.

Steps to reproduce

No response

System Info

Environment:
  Version  24.16.0
  Source   lts

Tool Paths:
  node  /Users/zoomelectrico/.vite-plus/js_runtime/node/24.16.0/bin/node
  npm   /Users/zoomelectrico/.vite-plus/js_runtime/node/24.16.0/bin/npm
  npx   /Users/zoomelectrico/.vite-plus/js_runtime/node/24.16.0/bin/npx

Package Manager:
  Name          pnpm
  Version       11.3.0
  Source        packageManager
  Source Path   /Users/zoomelectrico/Documents/@zoomelectrico/sinoparma/package.json
  Project Root  /Users/zoomelectrico/Documents/@zoomelectrico/sinoparma
  Bin Path      /Users/zoomelectrico/.vite-plus/package_manager/pnpm/11.3.0/pnpm/bin/pnpm



vp v0.1.24

Local vite-plus:
  vite-plus  v0.1.23

Tools:
  vite             v8.0.14
  rolldown         v1.0.3
  vitest           v4.1.7
  oxfmt            v0.52.0
  oxlint           v1.67.0
  oxlint-tsgolint  v0.23.0
  tsdown           v0.22.0

Environment:
  Package manager  pnpm v11.3.0
  Node.js          v24.16.0

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.

[jong-kyung]

Thanks for the report!
I tried to reproduce this from the information provided, but I couldn’t reproduce the hang.
Could you please provide a minimal reproduction?

[github-actions]

Hello @Zoomelectrico 👋

Please provide a minimal reproduction using a GitHub repository. This helps us understand and resolve your issue much faster.

A good reproduction should be:

• Minimal – include only the code necessary to demonstrate the issue
• Complete – contain everything needed to run and observe the problem
• Reproducible – consistently show the issue with clear steps

If no reproduction is provided, issues labeled needs reproduction will be closed after 3 days of inactivity.

For more context on why this is required, please read: https://antfu.me/posts/why-reproductions-are-required

[Zoomelectrico]

Hi @jong-kyung, I hope you're doing well! I'm trying to generate a new project using the CLI to create the minimal reproduction you need, but the linting gets stuck right at this stage of the CLI process.

At this point, I realize this might be an issue specific to my computer; however, honestly, I haven't done anything with any of the tools—(VP has only been installed on my computer for five days)—that would help me understand what might be causing it.

vp create @tanstack/start
VITE+ - The Unified Toolchain for the Web

◇ Which package manager would you like to use?
  pnpm

◇ pnpm@11.5.1 installed

◇ Which coding agent instruction files should Vite+ create?
  AGENTS.md, CLAUDE.md, .cursor/rules/viteplus.mdc

◇ Which editors are you using?
    Writes editor config files to enable recommended extensions and Oxlint/Oxfmt integrations.
  VSCode

◇ Initialize a git repository with an initial commit?
  Yes

◇ Set up pre-commit hooks to run formatting, linting, and type checking with auto-fixes?
  Yes


Generating project…

Running: pnpm dlx @tanstack/cli create --no-install --no-toolchain
┌  Let's configure your TanStack application
│
◇  Select framework:
│  React
│
◇  What would you like to name your project?
│  min-test
│
◇  Select deployment adapter:
│  Nitro (agnostic)
│
◇  Would you like to include demo/example pages?
│  No
│
◇  Keyboard Shortcuts ────────────────────────────────────────────────╮
│                                                                     │
│  Use ↑/↓ to navigate • Space to select/deselect • Enter to confirm  │
│                                                                     │
├─────────────────────────────────────────────────────────────────────╯
│
◇  What add-ons would you like for your project? (Space to toggle, Enter to confirm)
│  Sentry, Form, Shadcn, Table, PostHog
│
◇  Would you like to initialize a new git repository?
│  Yes
│
●  About to create:
│  
│    Project:         min-test
│    Location:        /Users/zoomelectrico/Documents/@zoomelectrico/min-test/min-test
│    Framework:       React
│    Mode:            file-router
│    Package manager: pnpm
│  
│    Deploy:          Nitro (agnostic)
│    Other add-ons:   Sentry, Form, Shadcn, Table, PostHog
│  
│    Initialize git:  yes
│    Install deps:    no
│    Agent skills:    no
│
◇  Continue with these settings?
│  Yes
│
◇  Initialized git repository
│
◇  Dependency installation skipped
│
◇  Installed additional shadcn components
│
└  Your TanStack app is ready in 'min-test'.

Use the following commands to start your app:
% cd min-test
% pnpm dev

Next steps:

Docs for the integrations you picked:
  • Nitro (agnostic) (deploy) — https://v3.nitro.build/

Please read the README.md file for information on testing, styling, adding routes, etc.


Wrote agent instructions to AGENTS.md

Linked CLAUDE.md to AGENTS.md

Linked .cursor/rules/viteplus.mdc to AGENTS.md
◇ .vscode/settings.json already exists.
    Vite+ adds VSCode settings for the built-in linter and formatter. Merge adds new keys without overwriting 
existing ones.
  Merge


Merged editor config into .vscode/settings.json

Wrote editor config to .vscode/extensions.json

✔ Rewrote types in min-test/tsconfig.json

Rewrote imports in one file

  min-test/vite.config.ts

✔ Merged staged config into min-test/vite.config.ts

✔ Git hooks configured
◇ Dependencies installed

◇ Code formatted

[jong-kyung]

@Zoomelectrico Thanks for the reproduction details! I was able to confirm the issue. I'll investigate further and follow up with updates.

[Zoomelectrico]

@jong-kyung Thank you very much!

[jong-kyung]

@fengmk2 I investigated this with a small reproduction:
https://github.com/jong-kyung/repro-vite-plus-1739

The issue seems to be that vp check --fix loads vite.config.ts, which can initialize heavy or side-effectful Vite plugins. In this reproduction, the TanStack/Nitro setup initializes nitro(...); the lint output is printed, but the process does not exit because the plugin appears to leave open handles.

Wrapping the plugin array with lazyPlugins avoids the hang:

plugins: lazyPlugins(() => [/* vite plugins */])

This still allows the plugins to run for dev / build / test / preview, while skipping them for lint / fmt / check.

I’m considering fixing this in create / migrate by automatically wrapping safe inline plugins: [...] arrays with lazyPlugins(() => [...]). For safety, this would skip cases that are already lazy, as well as dynamic or non-inline plugin expressions, and it would leave lint/fmt config resolution unchanged.

Before implementing this, I’d like to confirm the direction since lazyPlugins has been documented as an opt-in workaround so far, and this would make it automatic for safe inline plugin arrays.

[fengmk2]

@jong-kyung You can solve the problem this way according to your approach for now, and I expect lazyPlugins will exist for a while.