chore(deps): bump vite-plus to PR #1633 (pkg-pr-new)

[fengmk2]

Summary

Bump vite-plus and related @voidzero-dev/* packages to the pkg-pr-new prerelease for vite-plus PR #1633.

Updated where applicable:

• vite-plus → https://pkg.pr.new/voidzero-dev/vite-plus@1633
• vite alias → @voidzero-dev/vite-plus-core pkg-pr-new URL
• vitest alias → @voidzero-dev/vite-plus-test pkg-pr-new URL
• overrides / resolutions / pnpm.overrides / pnpm-workspace.yaml catalogs

Also configured minimum-release-age with vite-plus / @voidzero-dev/* excluded for pnpm / bun / npm.

Test plan

• CI passes

[gemini-code-assist]

Code Review

This pull request updates the vite-plus dependency to a specific build URL across multiple packages and introduces release age policies in .npmrc and pnpm-workspace.yaml. The review feedback identifies an incorrect configuration key in .npmrc, suggests using pnpm catalogs to manage the repeated dependency update more efficiently, and highlights unit inconsistencies and non-standard fields within the workspace configuration.

[gemini-code-assist]

In pnpm v10, the correct configuration key for excluding packages from the release age policy is min-release-age-policy-exclude. The current key min-release-age-exclude is likely invalid and will be ignored by the package manager.

min-release-age-policy-exclude=vite-plus,@voidzero-dev/*

[gemini-code-assist]

The PR description mentions updating vite and vitest aliases in overrides / resolutions, but these changes are missing from the diff. Please ensure these were not accidentally omitted from the commit.

Also, since vite-plus is updated to the same URL across multiple packages, consider using pnpm catalogs (v10+) in pnpm-workspace.yaml to manage this dependency centrally and avoid repetitive updates.

[gemini-code-assist]

The fields minimumReleaseAge and minimumReleaseAgeExclude are not standard for pnpm-workspace.yaml. Additionally, there is a unit inconsistency: .npmrc uses seconds (259200), while this file uses minutes (4320).

If these are intended for pnpm, they should be removed as they are already configured in .npmrc. If they are for a custom tool, consider standardizing the units and naming to match the package manager's configuration to avoid confusion and maintenance errors.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/bippy@5

commit: 4d2e28b