chore(deps): bump vite-plus to v0.2.2

[fengmk2]

Summary

Bump vite-plus and related packages to the pkg.pr.new prerelease build for v0.2.2 (registry-bridge commit build) to smoke-test the prerelease.

• vite-plus + vite (alias to @voidzero-dev/vite-plus-core) and vitest pinned to the commit build across deps / overrides / catalogs
• minimumReleaseAge enabled with the vite-plus / @voidzero-dev/* / oxc / oxlint stack excluded
• .npmrc (or .yarnrc.yml) points the package manager at the registry bridge (prerelease scaffolding)

Test plan

• CI passes

[gemini-code-assist]

Code Review

This pull request transitions the repository's testing and build configuration from Vitest and Vite to Vite Plus, updating package scripts, workspace catalogs, and test imports across multiple packages. The review feedback suggests combining duplicate imports in vite.config.ts and explicitly declaring vite-plus as a dependency in packages-private/vapor-e2e-test/package.json and packages/vue/package.json to ensure correct monorepo dependency resolution.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

To avoid duplicate imports from 'vite-plus', we can combine configDefaults and defineConfig into a single import statement. Please also remember to remove the duplicate import { defineConfig } from 'vite-plus' on line 3.

Suggested change

	import { configDefaults } from 'vite-plus'
	import { playwright } from 'vite-plus/test/browser-playwright'
	import { configDefaults, defineConfig } from 'vite-plus'
	import { playwright } from 'vite-plus/test/browser-playwright'

[gemini-code-assist]

Since the tests in this package import from 'vite-plus/test' and 'vite-plus/test/browser', we should explicitly declare 'vite-plus' as a dependency in package.json to ensure proper dependency resolution in the monorepo.

    "vitest": "catalog:",
    "vite-plus": "catalog:"

[gemini-code-assist]

Since the E2E tests in this package import from 'vite-plus/test' and 'vite-plus/test/browser', we should explicitly declare 'vite-plus' as a devDependency in package.json to ensure proper dependency resolution in the monorepo.

    "vitest": "catalog:",
    "vite-plus": "catalog:"