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

[fengmk2]

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)

Note: the bundled oxfmt/tsgolint in v0.2.0 flags a pre-existing TS(1038) in packages/varlet-cli/src/module.d.ts (redundant declare in an ambient context), so vp lint / vp check fail. Needs an upstream source fix; not addressed here.

Test plan

• CI passes

[pkg-pr-new]

Open in StackBlitz

@varlet/cli

npm i https://pkg.pr.new/@varlet/cli@9

@varlet/icons

npm i https://pkg.pr.new/@varlet/icons@9

@varlet/import-resolver

npm i https://pkg.pr.new/@varlet/import-resolver@9

@varlet/preset-tailwindcss

npm i https://pkg.pr.new/@varlet/preset-tailwindcss@9

@varlet/preset-unocss

npm i https://pkg.pr.new/@varlet/preset-unocss@9

@varlet/shared

npm i https://pkg.pr.new/@varlet/shared@9

@varlet/touch-emulator

npm i https://pkg.pr.new/@varlet/touch-emulator@9

@varlet/ui

npm i https://pkg.pr.new/@varlet/ui@9

@varlet/use

npm i https://pkg.pr.new/@varlet/use@9

@varlet/vite-plugins

npm i https://pkg.pr.new/@varlet/vite-plugins@9

commit: 2d0177e

[gemini-code-assist]

Code Review

This pull request updates dependency versions for Vite and Vitest, utilizing a temporary pkg.pr.new URL for vite-plus. It also attempts to configure overrides and security settings in pnpm-workspace.yaml. Feedback highlights that these configurations are unsupported in pnpm-workspace.yaml and must be placed in package.json and .npmrc respectively. Additionally, restoring the pnpm.overrides block in package.json is recommended, and the hardcoded temporary URL in the template generator's package.json should be replaced with a stable version range before merging.

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.

[gemini-code-assist]

The overrides, minimumReleaseAge, minimumReleaseAgeExclude, and blockExoticSubdeps configurations are not supported in pnpm-workspace.yaml and will be ignored by pnpm.

• Overrides: Must be defined in the root package.json under the pnpm.overrides field. Since you are using pnpm catalogs, you can restore the previous configuration in package.json pointing to "catalog:".
• Security Settings: minimumReleaseAge, minimumReleaseAgeExclude, and blockExoticSubdeps must be configured in .npmrc using kebab-case syntax (e.g., minimum-release-age = 60, block-exotic-subdeps = false).

[gemini-code-assist]

Restore the pnpm.overrides block here to ensure that vite and vitest are correctly overridden across the monorepo. Since you have defined the specific versions in the pnpm-workspace.yaml catalog, you can use "catalog:" here to automatically sync them.

Suggested change

	"packageManager": "pnpm@9.15.9"
	}
	"packageManager": "pnpm@9.15.9",
	"pnpm": {
	"overrides": {
	"vite": "catalog:",
	"vitest": "catalog:"
	}
	}
	}

[gemini-code-assist]

Using a hardcoded pkg.pr.new URL in a template generator's package.json means any project generated by users of this CLI will be locked to this specific temporary commit build.

While this might be necessary for temporary testing of this PR, please ensure this is replaced with a proper npm version range (e.g., ^0.2.0 or 0.2.0) before merging or releasing, to avoid breaking downstream users when the temporary build is cleaned up or if they require a stable release.