Skip to content

chore(deps): bump vite-plus to v0.2.0#9

Draft
fengmk2 wants to merge 2 commits into
mainfrom
update-vite-plus-prerelease-test-0.2.0
Draft

chore(deps): bump vite-plus to v0.2.0#9
fengmk2 wants to merge 2 commits into
mainfrom
update-vite-plus-prerelease-test-0.2.0

Conversation

@fengmk2

@fengmk2 fengmk2 commented Jun 17, 2026

Copy link
Copy Markdown
Owner

Summary

Bump vite-plus and related packages to the pkg.pr.new prerelease build for v0.2.0.

Updated where applicable:

  • vite-plus -> pkg.pr.new build
  • vite (alias/override -> @voidzero-dev/vite-plus-core)
  • vitest pinned to bundled 4.1.9 (the @voidzero-dev/vite-plus-test wrapper was removed upstream; vitest is now plain upstream)
  • pnpm field moved into pnpm-workspace.yaml (overrides), as the pnpm field in package.json is no longer read
  • minimumReleaseAge enabled with vite-plus packages excluded (pnpm-workspace.yaml)

Note: vp check surfaces 7 pre-existing typescript(TS6059) rootDir errors from the playground tsconfig, unrelated to this bump.

Test plan

  • CI passes

@fengmk2 fengmk2 self-assigned this Jun 17, 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 updates dependency versions in package.json and configures workspace overrides and release age exclusions in pnpm-workspace.yaml. The reviewer suggests pinning @vitest/coverage-v8 to 4.1.9 to match the pinned vitest version and prevent potential runtime errors. Additionally, the reviewer recommends adding vite-plus to the workspace overrides to ensure consistency across all sub-packages.

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 package.json
"vitest": "npm:@voidzero-dev/vite-plus-test@^0.1.14"
"vite": "https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856",
"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1856",
"vitest": "4.1.9"

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 vitest is pinned to 4.1.9, it is highly recommended to also pin @vitest/coverage-v8 (currently ^4.1.2 on line 35) to 4.1.9. Mismatched versions between vitest and @vitest/coverage-v8 can lead to runtime errors or unexpected behavior during coverage runs, as they rely on closely coupled internal APIs.

Comment thread pnpm-workspace.yaml
Comment on lines +4 to +6
overrides:
vite: https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856
vitest: 4.1.9

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

To ensure consistency across the entire workspace, consider adding vite-plus to the overrides list in pnpm-workspace.yaml. If any sub-packages or the playground depend on vite-plus, they might otherwise resolve to a different version (e.g., from the npm registry) instead of the prerelease build specified in the root package.json.

overrides:
  vite: https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856
  vite-plus: https://pkg.pr.new/voidzero-dev/vite-plus@1856
  vitest: 4.1.9

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