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)

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 to prerelease URLs and moves several pnpm configuration settings, such as overrides and release age rules, from the root package.json to pnpm-workspace.yaml. Feedback highlights that these pnpm configurations are not supported in pnpm-workspace.yaml and must be restored to the root package.json to prevent them from being ignored. Additionally, the specified vitest version 4.1.9 does not exist and needs to be corrected to a valid version to avoid installation failures.

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 +121 to +161
minimumReleaseAge: 60
minimumReleaseAgeExclude:
- "@voidzero-dev/*"
- vite-plus
- "@vitest/*"
- vite
- vitest
- "@oxc-project/*"
- "@oxlint/*"
- oxlint
- oxfmt
- oxlint-tsgolint
blockExoticSubdeps: false

onlyBuiltDependencies:
- esbuild

overrides:
"@azure/msal-node>uuid": "11.1.1"
"@unhead/vue": "2.1.15"
defu: "6.1.7"
devalue: "5.8.1"
dompurify: "3.4.10"
esbuild: "0.28.1"
h3: "1.15.11"
hono: "4.12.25"
launch-editor: "2.14.1"
nanotar: "0.3.0"
nitropack: "2.13.4"
node-forge: "1.4.0"
nuxt: "4.4.8"
qs: "6.15.2"
shell-quote: "1.8.4"
simple-git: "3.36.0"
srvx: "0.11.15"
svgo: "4.0.1"
tar: "7.5.16"
"vite@>=7.0.0 <7.3.5": "7.3.5"
yaml: "2.9.0"
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.

high

The configuration options minimumReleaseAge, minimumReleaseAgeExclude, blockExoticSubdeps, onlyBuiltDependencies, and overrides are not supported in pnpm-workspace.yaml. In pnpm, these settings must be defined in the root package.json under the "pnpm" field. Placing them here will cause pnpm to ignore them, meaning your overrides (including the critical override for vite to use the vite-plus-core prerelease) will not be applied.

Comment thread package.json
Comment on lines +23 to 24
"packageManager": "pnpm@10.0.0"
}

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

Restore the "pnpm" configuration block in the root package.json so that the overrides, allowed built dependencies, and minimum release age settings are correctly applied by pnpm.

  "packageManager": "pnpm@10.0.0",
  "pnpm": {
    "minimumReleaseAge": 60,
    "minimumReleaseAgeExclude": [
      "@voidzero-dev/*",
      "vite-plus",
      "@vitest/*",
      "vite",
      "vitest",
      "@oxc-project/*",
      "@oxlint/*",
      "oxlint",
      "oxfmt",
      "oxlint-tsgolint"
    ],
    "blockExoticSubdeps": false,
    "onlyBuiltDependencies": [
      "esbuild"
    ],
    "overrides": {
      "@azure/msal-node>uuid": "11.1.1",
      "@unhead/vue": "2.1.15",
      "defu": "6.1.7",
      "devalue": "5.8.1",
      "dompurify": "3.4.10",
      "esbuild": "0.28.1",
      "h3": "1.15.11",
      "hono": "4.12.25",
      "launch-editor": "2.14.1",
      "nanotar": "0.3.0",
      "nitropack": "2.13.4",
      "node-forge": "1.4.0",
      "nuxt": "4.4.8",
      "qs": "6.15.2",
      "shell-quote": "1.8.4",
      "simple-git": "3.36.0",
      "srvx": "0.11.15",
      "svgo": "4.0.1",
      "tar": "7.5.16",
      "vite@>=7.0.0 <7.3.5": "7.3.5",
      "yaml": "2.9.0",
      "vite": "https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856",
      "vitest": "3.0.0"
    }
  }
}

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

high

The version "4.1.9" for vitest does not exist (Vitest's latest major version is 3.x). This will cause pnpm install to fail with a resolution error. Please correct this to a valid Vitest version (such as 3.0.0 or the intended version).

    vitest: "3.0.0"

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