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 transitions several core dependencies, including vite, vite-plus, and vitest, from npm registry versions to preview builds hosted on pkg.pr.new. It also updates various oxc and oxlint related packages and introduces unrun as an optional dependency. Feedback focused on the risk of non-reproducible builds caused by using PR-based URLs instead of pinned commit hashes. The reviewer suggested utilizing the Yarn catalog: protocol to improve maintainability and ensure dependency stability.

[gemini-code-assist]

Critical Issue: Non-Reproducible Builds

The current yarn.lock file contains unresolved pkg.pr.new URLs with PR numbers (e.g., @1633) instead of being pinned to specific commit hashes. This can lead to non-reproducible builds, as the dependency can change if new commits are pushed to the PR branch.

To fix this and improve maintainability, it's recommended to use the catalog: protocol for dependencies defined in your .yarnrc.yml catalog. This is the idiomatic approach for Yarn Berry and can help ensure dependencies are correctly resolved and pinned.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1633",
	"vite-plus": "catalog:vite-plus",

[gemini-code-assist]

High Severity: Non-Reproducible Builds in Resolutions

The resolutions field also uses URLs with PR numbers, which can lead to non-reproducible builds for the same reason mentioned in the comment on vite-plus. Since you are using Yarn Berry and have a catalog defined in .yarnrc.yml, you can leverage it here as well.

Using the catalog: protocol avoids duplicating URLs and should help in correctly pinning the vitest dependency to a commit hash in yarn.lock.

Suggested change

	"vite": "https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1633",
	"vitest": "https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-test@1633"
	"vite": "catalog:vite",
	"vitest": "catalog:vitest"