chore(deps): bump vite-plus to v0.2.2#10
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request configures a registry bridge in .npmrc, migrates vite, vite-plus, and vitest dependencies to use pnpm catalogs in package.json and pnpm-workspace.yaml, and configures release age exclusions. The reviewer provided several recommendations to align with the Vite+ v0.2.x migration guide, such as removing vitest from devDependencies, overrides, and catalog if it is not directly imported, removing vitest from minimumReleaseAgeExclude since it is now a stable upstream release, and cleaning up obsolete peerDependencyRules for vitest.
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.
| "vite": "catalog:", | ||
| "vite-plus": "catalog:", | ||
| "vitest": "catalog:" |
There was a problem hiding this comment.
With the upgrade to Vite+ v0.2.x, the @voidzero-dev/vite-plus-test wrapper package has been removed, and vitest is now consumed directly and transitively via vite-plus.
If this project does not have direct vitest imports (i.e., you only run tests via vp test and do not import from vitest directly), you can completely remove vitest from devDependencies (Case A in the Vite+ migration guide).
"vite": "catalog:",
"vite-plus": "catalog"| - '@mizdra/*' | ||
| - vitest | ||
| - '@vitest/*' |
There was a problem hiding this comment.
Since vitest is now upstream vitest (a stable release, not a commit build), it does not need to be excluded from minimumReleaseAge.
- '@mizdra/*'| overrides: | ||
| vite: '$vite' | ||
| vitest: '$vitest' | ||
| vite: 'catalog:' | ||
| vitest: 'catalog:' |
There was a problem hiding this comment.
If you are following Case A (removing vitest because it is not directly imported), you should also remove vitest from the overrides block in pnpm-workspace.yaml.
overrides:
vite: 'catalog:'| peerDependencyRules: | ||
| allowAny: | ||
| - vite | ||
| - vitest | ||
| allowedVersions: | ||
| vite: '*' | ||
| vitest: '*' |
There was a problem hiding this comment.
According to the Vite+ v0.2.x migration guide, you should remove any peerDependencyRules entries for vitest (such as allowAny and allowedVersions) since the @voidzero-dev/vite-plus-test wrapper has been removed and vitest is now consumed directly.
peerDependencyRules:
allowAny:
- vite
allowedVersions:
vite: '*'| catalog: | ||
| vite: npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251 | ||
| vitest: 4.1.9 | ||
| vite-plus: 0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251 |
There was a problem hiding this comment.
If vitest is not directly imported and you are removing it (Case A), you should also remove it from the catalog block in pnpm-workspace.yaml.
catalog:
vite: npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251
vite-plus: 0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad32511 participant
Summary
Bump
vite-plusand 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) andvitestpinned to the commit build across deps / overrides / catalogsminimumReleaseAgeenabled with thevite-plus/@voidzero-dev/*/ oxc / oxlint stack excluded.npmrc(or.yarnrc.yml) points the package manager at the registry bridge (prerelease scaffolding)Test plan