Skip to content

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

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#23
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)
  • @vitest/browser-playwright added (4.1.9) since the browser provider is now an optional peer dep used by vite.config.ts
  • minimumReleaseAge enabled with vite-plus packages excluded (pnpm/bun/npm as applicable)

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 dependencies, including vite-plus, vitest, and vite overrides, to use specific pre-release builds or version 4.1.9. It also adds pnpm configurations (minimumReleaseAge, minimumReleaseAgeExclude, and blockExoticSubdeps) to pnpm-workspace.yaml. Feedback indicates that these configuration options are placed in the wrong file and format; they must be moved to .npmrc using kebab-case to prevent them from being silently ignored by pnpm.

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 +61 to +74
minimumReleaseAge: 60
minimumReleaseAgeExclude:
- '@voidzero-dev/*'
- vite-plus
- '@vitest/*'
- vite
- vitest
- '@oxc-project/*'
- '@oxlint/*'
- oxlint
- oxfmt
- oxlint-tsgolint

blockExoticSubdeps: false

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

The settings minimumReleaseAge, minimumReleaseAgeExclude, and blockExoticSubdeps are pnpm configuration options. In pnpm, these settings must be defined in the .npmrc file using kebab-case (e.g., minimum-release-age, minimum-release-age-exclude, and block-exotic-subdeps), rather than in pnpm-workspace.yaml in camelCase.\n\nPlacing them here will cause them to be silently ignored by pnpm.\n\nPlease move these configurations to your .npmrc file:\n\nini\nminimum-release-age=60\nminimum-release-age-exclude[]=@voidzero-dev/*\nminimum-release-age-exclude[]=vite-plus\nminimum-release-age-exclude[]=@vitest/*\nminimum-release-age-exclude[]=vite\nminimum-release-age-exclude[]=vitest\nminimum-release-age-exclude[]=@oxc-project/*\nminimum-release-age-exclude[]=@oxlint/*\nminimum-release-age-exclude[]=oxlint\nminimum-release-age-exclude[]=oxfmt\nminimum-release-age-exclude[]=oxlint-tsgolint\nblock-exotic-subdeps=false\n

# Note: pnpm configuration options (minimumReleaseAge, etc.) must be defined in .npmrc

@github-actions

Copy link
Copy Markdown

e18e dependency analysis

No dependency warnings found.

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