chore(deps): bump vite-plus to pkg-pr-new pr-1588

[fengmk2]

Summary

Bump vite-plus to pkg-pr-new build for PR #1588 (replace @voidzero-dev/vite-plus-test with upstream vitest@4.1.5).

Test plan

• CI passes

[gemini-code-assist]

Code Review

This pull request updates dependency versions across multiple package.json files to use pkg.pr.new builds for vite-plus and related @voidzero-dev packages, and adds a .npmrc file with release age configurations. The review feedback consistently identifies a version mismatch issue across all modified package.json files: vite-plus is specified using a PR number (@1588), while the overridden core and prompt packages are pinned to a specific commit hash. To ensure reproducible builds and prevent API drift, it is recommended to pin vite-plus to the exact same commit hash.

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e",

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e",

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588"
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e"

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e",

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e",

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588"
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e"

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e",

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e",

[gemini-code-assist]

There is a mismatch between the version specifier used for vite-plus (which uses the PR number @1588) and the overrides for @voidzero-dev/vite-plus-core and @voidzero-dev/vite-plus-prompts (which use the specific commit hash @5577b0154f33d1480a3c96347e94fa5d2094de2e). If new commits are pushed to PR 1588, vite-plus will resolve to the newer commit while the overridden packages will remain pinned to the older commit, potentially causing runtime errors or build failures due to API drift. It is highly recommended to pin vite-plus to the exact same commit hash to ensure consistency and reproducible builds.

Suggested change

	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@1588",
	"vite-plus": "https://pkg.pr.new/voidzero-dev/vite-plus@5577b0154f33d1480a3c96347e94fa5d2094de2e",