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)
• @vitest/coverage-v8 pinned to 4.1.9 (the ci script runs with --coverage)
• minimumReleaseAge enabled with vite-plus packages excluded (pnpm/bun/npm as applicable)

Note: the existing templates/routing-fallback source has pre-existing type errors (TS2307 @faasjs/core, TS7031 implicit any) unrelated to this bump; they are not introduced here.

Test plan

• CI passes

[gemini-code-assist]

Code Review

This pull request updates the project's testing and build dependencies, replacing the custom @voidzero-dev/vite-plus-test package with standard vitest (v4.1.9) and updating vite and vite-plus to use prerelease builds from pkg.pr.new. The review feedback correctly identifies a critical issue where temporary pkg.pr.new prerelease URLs are specified in the create-faas-app templates (admin and minimal). Since these templates are copied by end-users to bootstrap new applications, pointing to temporary commit-based builds will eventually lead to broken installations. It is highly recommended to use stable npm version ranges in these templates instead.

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]

Using a temporary pkg.pr.new prerelease URL in the template's overrides is problematic because this template is copied when users create new applications via create-faas-app. Any generated app will permanently point to this specific commit-based prerelease build of vite-plus-core, which can lead to broken installations or rate-limiting once the prerelease build is removed. These overrides should be updated to stable npm version ranges (e.g., ^0.2.0 or 0.2.0) to prevent issues for end-users.

Suggested change

	"overrides": {
	"vite": "npm:@voidzero-dev/vite-plus-core",
	"vitest": "npm:@voidzero-dev/vite-plus-test"
	"vite": "https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856",
	"vitest": "4.1.9"
	},
	"overrides": {
	"vite": "npm:@voidzero-dev/vite-plus-core@^0.2.0",
	"vitest": "4.1.9"
	},

[gemini-code-assist]

Using a temporary pkg.pr.new prerelease URL in the template's overrides is problematic because this template is copied when users create new applications via create-faas-app. Any generated app will permanently point to this specific commit-based prerelease build of vite-plus-core, which can lead to broken installations or rate-limiting once the prerelease build is removed. These overrides should be updated to stable npm version ranges (e.g., ^0.2.0 or 0.2.0) to prevent issues for end-users.

Suggested change

	"overrides": {
	"vite": "npm:@voidzero-dev/vite-plus-core",
	"vitest": "npm:@voidzero-dev/vite-plus-test"
	"vite": "https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856",
	"vitest": "4.1.9"
	},
	"overrides": {
	"vite": "npm:@voidzero-dev/vite-plus-core@^0.2.0",
	"vitest": "4.1.9"
	},