[Dunqing]

vp migrate leaves some packages' imports alone: vite imports when the package lists vite in dependencies or peerDependencies or is a published plugin (vite-plugin-*, unplugin-*), and vitest imports when it lists vitest there. That code runs in projects that may not use Vite+. prefer-vite-plus-imports doesn't know these skips, so it reports the same imports, and its autofix rewrites them. With vite-plus 1.2.0, in a package with vitest in peerDependencies:

before: import { expect } from "vitest";
after:  import { expect } from "vite-plus/test";   (vp lint --fix)

New projects run vp check --fix from the pre-commit hook, so this happens on commit, and the package then breaks for its plain Vitest users.

For vite the rule only reports config files, which aren't published, so that half only removes lint errors that vp migrate itself leaves behind; the vitest half prevents the breakage.

The rule now applies the same skips, read from the nearest package.json like its Nuxt and Oxlint exemptions. A vite or vitest devDependency alone still gets the imports reported, as in the migrator. tsdown needs nothing, since the rule doesn't rewrite it. Two existing spec cases linted a file inside packages/cli as an ordinary file; they move to a fixture, because vite-plus itself depends on vite and vitest.

The rule has picked up the migrator's skips one at a time (#2004's config-file scope, the Oxlint API owners in #2328, Nuxt test utils in #2551). Sharing the skip rules between import_rewriter.rs and the rule, as vite-config-entry-basenames.json already does for config file names, would stop them drifting again. This PR doesn't do that.

[fengmk2]

@Dunqing please handle the conflicts.

[Dunqing]

@Dunqing please handle the conflicts.

Done!