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)
  • minimumReleaseAge enabled with vite-plus packages excluded (pnpm/bun/npm as applicable)
  • moved the pnpm.overrides field from package.json into pnpm-workspace.yaml (the pnpm field is no longer read by pnpm)

Test plan

  • CI passes

@fengmk2 fengmk2 self-assigned this Jun 17, 2026
@pkg-pr-new

pkg-pr-new Bot commented Jun 17, 2026

Copy link
Copy Markdown

Open in StackBlitz

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

commit: 361ee38

@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 the dependency versions and overrides for vite, vitest, and vite-plus in pnpm-workspace.yaml. It also introduces configuration options like minimumReleaseAge, minimumReleaseAgeExclude, and blockExoticSubdeps. However, these are .npmrc settings and are not supported inside pnpm-workspace.yaml, so they should be moved to the root .npmrc file to be properly applied.

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 +30 to +42
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 configuration options minimumReleaseAge, minimumReleaseAgeExclude, and blockExoticSubdeps are .npmrc settings and are not recognized or supported inside pnpm-workspace.yaml. Keeping them here will cause pnpm to ignore them, meaning the minimum release age checks and exclusions will not be applied.\n\nThese settings should be moved to your root .npmrc file using kebab-case:\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

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