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
@pkg-pr-new

pkg-pr-new Bot commented Jul 2, 2026

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/trpc-nuxt@11

commit: ec1f4a6

@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 adds a registry bridge to .npmrc, configures release age exclusions in pnpm-workspace.yaml, and pins vite and vite-plus to specific commit versions. It also adds vitest to the test application's dependencies and updates its version in the workspace catalog. The reviewer advises that since Vite+ v0.2.0 transitively manages vitest directly, manually declaring vitest in package.json and cataloging/overriding it in pnpm-workspace.yaml is redundant and should be removed.

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 apps/test/package.json
Comment on lines +23 to +24
"@playwright/test": "1.60.0",
"vitest": "catalog:"

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

Starting with Vite+ v0.2.0, the @voidzero-dev/vite-plus-test wrapper has been removed, and vite-plus now transitively installs and manages the upstream vitest dependency directly. As a result, you no longer need to manually declare vitest in your package dependencies. Removing it prevents potential version mismatch issues and simplifies your dependency tree.

    "@playwright/test": "1.60.0"

Comment thread pnpm-workspace.yaml
Comment on lines +32 to +34
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

Since Vite+ v0.2.0+ consumes upstream vitest directly and the @voidzero-dev/vite-plus-test wrapper has been removed, you no longer need to override or catalog vitest. You should remove vitest from the catalog here, and also remove vitest: 'catalog:' from the overrides section below to clean up unused configuration.

  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