Skip to content

chore(deps): bump vite-plus to 0.1.21-alpha.7#3

Draft
fengmk2 wants to merge 2 commits into
mainfrom
update-vite-plus-alpha-0.1.21-alpha.7
Draft

chore(deps): bump vite-plus to 0.1.21-alpha.7#3
fengmk2 wants to merge 2 commits into
mainfrom
update-vite-plus-alpha-0.1.21-alpha.7

Conversation

@fengmk2
Copy link
Copy Markdown
Owner

@fengmk2 fengmk2 commented May 13, 2026

Summary

Bump vite-plus and related packages to alpha 0.1.21-alpha.7.

Updated where applicable:

  • vite-plus
  • vitest (alias to @voidzero-dev/vite-plus-test)
  • vite (alias to @voidzero-dev/vite-plus-core)
  • overrides / resolutions / pnpm.overrides / pnpm-workspace.yaml catalogs
  • minimumReleaseAgeExclude / minimumReleaseAgeExcludes configured for pnpm + bun

Test plan

  • CI passes

@fengmk2 fengmk2 self-assigned this May 13, 2026
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates several package.json files to pin the versions of @voidzero-dev/vite-plus-core, @voidzero-dev/vite-plus-test, and vite-plus to 0.1.21-alpha.7. A review comment suggests using version ranges (e.g., >=0.1.21-alpha.7) instead of hard-pinned versions for peerDependencies to improve compatibility and maintain consistency with other dependency definitions in the project.

Comment thread packages/dev/package.json
Comment on lines +62 to +66
"@voidzero-dev/vite-plus-core": "0.1.21-alpha.7",
"@voidzero-dev/vite-plus-test": "0.1.21-alpha.7",
"jsdom": "*",
"typescript": "*",
"vite-plus": "*"
"vite-plus": "0.1.21-alpha.7"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For peerDependencies, it is generally recommended to use a version range (e.g., >=0.1.21-alpha.7) rather than a hard-pinned version. This provides better compatibility for consumers of the package and avoids potential version conflicts when minor updates or bug fixes are released in subsequent alpha versions. This would also be consistent with how other peer dependencies like @faasjs/core are defined in this file.

Suggested change
"@voidzero-dev/vite-plus-core": "0.1.21-alpha.7",
"@voidzero-dev/vite-plus-test": "0.1.21-alpha.7",
"jsdom": "*",
"typescript": "*",
"vite-plus": "*"
"vite-plus": "0.1.21-alpha.7"
"@voidzero-dev/vite-plus-core": ">=0.1.21-alpha.7",
"@voidzero-dev/vite-plus-test": ">=0.1.21-alpha.7",
"jsdom": "*",
"typescript": "*",
"vite-plus": ">=0.1.21-alpha.7"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant