Skip to content

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

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

chore(deps): bump vite-plus to v0.2.0#8
fengmk2 wants to merge 3 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)
  • @vitest/browser-playwright added at 4.1.9 (vitest 4 split the browser providers into separate packages; the config imports the playwright provider)
  • minimumReleaseAge enabled with vite-plus packages excluded (pnpm-workspace.yaml)

Note: vp check surfaces ~11 pre-existing eslint(no-underscore-dangle) errors in docs/scripts, 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 several dependency versions in the pnpm workspace catalog, including using pkg.pr.new URLs for Vite and updating Vitest to version 4.1.9. It also adds @vitest/browser-playwright to package.json and configures release age exclusions in pnpm-workspace.yaml. The review feedback suggests centralizing the new @vitest/browser-playwright dependency in the pnpm catalog and referencing it via catalog: to maintain consistent dependency management.

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
"@rspack/core": "^1.7.3",
"@svitejs/changesets-changelog-github-compact": "^1.2.0",
"@typescript/native-preview": "7.0.0-dev.20260421.2",
"@vitest/browser-playwright": "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 and centralize dependency management, @vitest/browser-playwright should be defined in the pnpm catalog and referenced here using catalog:, similar to vitest and esbuild.

Suggested change
"@vitest/browser-playwright": "4.1.9",
"@vitest/browser-playwright": "catalog:",

Comment thread pnpm-workspace.yaml
vitest: npm:@voidzero-dev/vite-plus-test@latest
vite-plus: latest
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

Add @vitest/browser-playwright to the catalog so it can be referenced via catalog: in package.json. This keeps all Vitest-related dependencies centrally managed and in sync.

  vitest: 4.1.9
  "@vitest/browser-playwright": 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