Revert bundling Vitest directly inside Vite+

まず Vite+ のパッケージエクスポートと依存関係のオーバーライド設定を追跡し、次に npm のエイリアス例および以前の @voidzero-dev/vite-plus-test のセットアップと比較します。vitest パッケージをインポートする、またはプログラムから使用するインテグレーションが、vite-plus/test への移行を必要とせずに Vite+ で解決されれば完了です。

Description

Currently, there is no way to add an import subpath as a package override (example below)

{
    "devDependencies": {
        "vitest": "npm:vite-plus@0.2.8/test" // doesn't work!
    }
}

This means that, despite supposedly being compatible with Vitest, packages and integrations may break now due to the absence of a vitest package to import from.

Suggested solution

The old setup of overriding vitest with @voidzero-dev/vite-plus-test worked fine for this purpose. I propose that we bring it back, at least temporarily, if the Vite+ core team is dead set on bundling it. This way, integrations that check for the vitest package still work with Vite+.

Alternative

Alternatives include migrating the entire ecosystem to use the vite-plus/test export which seems unlikely to happen (and also would break compatibility with vanilla Vitest unless packages have to check for both exports, which is another optional peer dependency required to be declared).

Additional context

This isn't as much of a problem for Vite, tsdown, Rolldown, and Oxlint because their requirements are type-level imports or (in the case of Vite) is already bypassed by overriding the vite package. On the other hand, some Vitest reporters rely on extending existing reporters or programmatically running Vitest, which isn't covered in the current export model.

Validations

• Read the Contributing Guidelines.
• Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
• Check that there isn't already an issue requesting the same feature.