`vp migrate` exits early when `vite-plus` is already installed, leaving Vite imports and scripts unmigrated

[jong-kyung]

Describe the bug

When a project has been partially or manually migrated to Vite+ by installing vite-plus first, vp migrate appears to treat the project as already migrated and skips the remaining core migration steps.

This can happen during manual migration workflows where the user first adds vite-plus / Vite+ dependencies and then runs vp migrate to finish the migration.

In that state, vp migrate can still merge some config into vite.config.ts such as lint, but it does not rewrite the existing Vite imports or scripts.

Expected behavior:

• vite.config.ts imports should be rewritten from vite to vite-plus
• vite/client references should be rewritten to vite-plus/client
• package scripts such as vite, vite build, and vite preview should be rewritten to vp dev, vp build, and vp preview
• the migration should only report “already using Vite+” once the project is actually migrated, not merely because vite-plus exists in package.json

Actual behavior:

• vite.config.ts still contains:

import { defineConfig } from 'vite'

• package.json scripts still contain:

{
 "dev": "vite",
 "build": "tsc -b && vite build",
 "preview": "vite preview"
}

• tsconfig.app.json still contains:

"types": ["vite/client"]

• vp lint . reports vite-plus/prefer-vite-plus-imports against vite.config.ts.

It looks like the migration completion condition may be too broad. Instead of considering the project migrated when
vite-plus is present in dependencies, vp migrate may need to verify that core migration steps have completed, or
continue running idempotent rewrites for imports, scripts, and tsconfig types.

Reproduction

https://github.com/jong-kyung/repro-vite-plus-1817

Steps to reproduce

npm create vite@latest manual-vp-migrate -- --template react-ts
cd manual-vp-migrate
npm install

npm remove vite
npm install -D vite-plus @voidzero-dev/vite-plus-core

vp migrate --no-interactive

Observed result:

• vite.config.ts still imports from vite
• scripts still call vite
• tsconfig.app.json still references vite/client
• vp lint . reports that vite-plus imports should be used

System Info

VITE+ - The Unified Toolchain for the Web

Environment:
Version  24.16.0
Source   lts

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

Package Manager:
Name          npm
Version       11.16.0
Source        devEngines.packageManager
Source Path   /Users/jong-kyung/Desktop/jklee/dev/manual-vp-migrate/package.json
Project Root  /Users/jong-kyung/Desktop/jklee/dev/manual-vp-migrate
Bin Path      /Users/jong-kyung/.vite-plus/package_manager/npm/11.16.0/npm/bin/npm

Used Package Manager

npm

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]

I think the “already using Vite+” check may need to be stricter than only checking whether vite-plus exists in package.json.

vite-plus/packages/cli/src/migration/bin.ts

Line 914 in 8271eaf

if (hasVitePlusDependency(rootPkg) && !isForceOverrideMode()) {

Since the README also documents a manual setup path, users may run vp migrate after performing the manual setup.

vite-plus/README.md

Line 184 in 8271eaf

#### Manual Installation & Migration

In that case, treating the presence of vite-plus in package.json as proof that the migration is complete can
miss partially migrated projects, so I think the completion check for vp migrate should be improved.

[fengmk2]

This issue does exist, and we can continue improving it. 👍

[jong-kyung]

@fengmk2 I’ll prepare a PR to improve this. My plan is to update the early-exit condition so that vp migrate only
reports “already using Vite+” when no legacy migration signals remain, instead of treating the presence of vite-plus in package.json as sufficient proof that migration is complete.