Skip to content

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

Draft
fengmk2 wants to merge 3 commits into
minorfrom
update-vite-plus-alpha-0.1.21-alpha.7
Draft

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

Conversation

@fengmk2

@fengmk2 fengmk2 commented May 13, 2026

Copy link
Copy Markdown
Owner

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

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

Copy link
Copy Markdown

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 the versions of vitest, vite-plus, and vite to specific alpha releases and adds a minimumReleaseAgeExclude section to the workspace configuration. The reviewer suggests centralizing dependency management by adding vitest and vite-plus to the workspace catalog and using the catalog: protocol in package.json. There is also a concern regarding the placement of the minimumReleaseAgeExclude field, which may not be a standard pnpm-workspace.yaml property, along with a suggestion to use single quotes for consistency.

Comment thread pnpm-workspace.yaml
'entities': '^7.0.1'
'estree-walker': ^2.0.2
'vite': npm:@voidzero-dev/vite-plus-core@latest
'vite': npm:@voidzero-dev/vite-plus-core@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

To improve maintainability and ensure version consistency across the workspace, consider adding vitest and vite-plus to the catalog. This centralizes version management for the entire vite-plus suite, following the pattern already established for vite.

  'vite': npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7
  'vitest': npm:@voidzero-dev/vite-plus-test@0.1.21-alpha.7
  'vite-plus': 0.1.21-alpha.7

Comment thread package.json
Comment on lines +91 to +92
"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.21-alpha.7",
"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

Since vite is already using the workspace catalog, it is recommended to do the same for vitest and vite-plus (after adding them to the catalog in pnpm-workspace.yaml). This keeps the root package.json clean and ensures all packages in the workspace use the same versions.

Suggested change
"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.21-alpha.7",
"vite-plus": "0.1.21-alpha.7"
"vitest": "catalog:",
"vite-plus": "catalog:"

Comment thread pnpm-workspace.yaml Outdated
Comment on lines +31 to +33
minimumReleaseAgeExclude:
- vite-plus
- "@voidzero-dev/*"

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

Regarding the minimumReleaseAgeExclude configuration:

  1. Configuration Location: This is not a standard top-level field for pnpm-workspace.yaml in pnpm or bun. For pnpm, this setting typically belongs in .npmrc as minimum-release-age-exclude. If this is intended for a custom tool, please verify the location; otherwise, it might be ignored by the package managers.
  2. Style Consistency: Use single quotes for '@voidzero-dev/*' to match the established style in the rest of the file (e.g., lines 6, 7, 11).
minimumReleaseAgeExclude:
  - vite-plus
  - '@voidzero-dev/*'

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