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 configures a preview build registry bridge in .npmrc, updates dependencies in package.json and pnpm-workspace.yaml to use specific catalog versions for vite, vite-plus, and vitest, and updates test helpers to import page from vite-plus/test/context. Feedback is provided regarding the global disabling of strictPeerDependencies in pnpm-workspace.yaml, which should remain enabled to prevent silent runtime bugs and dependency mismatches.

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]

Disabling strictPeerDependencies globally (strictPeerDependencies: false) is a heavy-handed approach that bypasses peer dependency validation for all packages in the workspace. This can lead to silent runtime bugs, incompatible packages, or duplicate package instances (e.g., multiple versions of React) in the dependency tree.\n\nSince this workspace already has a peerDependencyRules section configured to handle specific peer dependency mismatches (like vite and vitest), it is highly recommended to keep strictPeerDependencies: true and add any new peer dependency exceptions to peerDependencyRules instead.

strictPeerDependencies: true