Skip to content

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

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#11
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 configures a custom registry bridge in .npmrc, adds vite as a catalog dependency in create-remdx and remdx, and updates pnpm-workspace.yaml with release age constraints and specific commit-based versions for vite and vite-plus. Feedback on these changes suggests removing vitest from the catalog, overrides, and peer dependency rules, as it is now transitively consumed through vite-plus and no longer required directly in this workspace.

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 +24 to +26
vite: npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251
vitest: 4.1.9
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

According to the official vite-plus v0.2.x upgrade guide, the @voidzero-dev/vite-plus-test wrapper package has been removed, and vitest is now consumed directly and transitively through vite-plus [1.2.1].

Since this workspace does not have any direct vitest dependencies or custom browser-mode test requirements, you should completely remove vitest from the dependency-resolution mechanisms to avoid unnecessary overrides:

  1. Remove vitest: 4.1.9 from catalog (line 25).
  2. Remove vitest: 'catalog:' from overrides (line 29).
  3. Remove vitest from peerDependencyRules (lines 33 and 36).
  vite: npm:@voidzero-dev/vite-plus-core@0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251
  vite-plus: 0.0.0-commit.1d7ba811f0e456640b0e761e8e8acf77d1ad3251

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