Skip to content

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

Draft
fengmk2 wants to merge 1 commit into
mainfrom
update-vite-plus-prerelease-test-0.2.2
Draft

chore(deps): bump vite-plus to v0.2.2#5
fengmk2 wants to merge 1 commit into
mainfrom
update-vite-plus-prerelease-test-0.2.2

Conversation

@fengmk2

@fengmk2 fengmk2 commented Jul 2, 2026

Copy link
Copy Markdown
Owner

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

@fengmk2 fengmk2 self-assigned this Jul 2, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request migrates the project's testing and build configuration to use vite-plus instead of standard vite and vitest. This involves updating test imports to vite-plus/test, adjusting configuration files, adding a .npmrc registry bridge, and introducing a pnpm-workspace.yaml workspace configuration with catalog dependencies. Feedback on the workspace configuration suggests removing redundant commit-pinned package exclusions that are already covered by broader wildcard rules.

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.

Comment thread pnpm-workspace.yaml
Comment on lines +15 to +25
- rolldown
- '@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-darwin-arm64@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-darwin-x64@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-linux-arm64-gnu@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-linux-arm64-musl@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-linux-x64-gnu@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-linux-x64-musl@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-win32-arm64-msvc@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- '@voidzero-dev/vite-plus-win32-x64-msvc@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'
- 'vite-plus@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251'

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The specific commit-pinned package exclusions on lines 16–25 are redundant because vite-plus (on line 3) and '@voidzero-dev/*' (on line 4) already cover them. Removing these redundant entries simplifies the configuration and avoids having to update these commit hashes in multiple places during future dependency bumps.

  - rolldown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant