Skip to content

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

Draft
fengmk2 wants to merge 2 commits into
developmentfrom
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
developmentfrom
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 vite, vite-plus, and vitest to 0.1.21-alpha.7 across the main frontend and multiple widget packages. It also introduces pnpm-workspace.yaml files to exclude these packages from minimum release age checks. The reviewer suggests centralizing the workspace configuration at the repository root to reduce duplication and improve maintainability. Additionally, it is recommended to include vite-plus in the overrides section of the package.json files to ensure version consistency throughout the dependency tree.

Comment thread src/frontend/package.json
Comment on lines +154 to +155
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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 you are bumping vite-plus to an alpha version and overriding its core components (vite and vitest), it is recommended to also include vite-plus in the overrides section. This ensures that any transitive dependencies or other packages in the tree that might depend on vite-plus are forced to use the same alpha version, maintaining consistency across the project.

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

Comment on lines +1 to +3
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

The addition of identical pnpm-workspace.yaml files across multiple subdirectories (src/frontend, src/widgets/...) suggests a fragmented workspace setup. If these projects are part of a single monorepo, it would be much more maintainable to have a single pnpm-workspace.yaml at the repository root. This would allow you to centralize configurations like minimumReleaseAgeExclude and leverage pnpm catalogs (which you mentioned in the PR description) to manage shared dependency versions centrally instead of repeating them in every package.json.

Comment on lines +33 to +34
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

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

Comment on lines +37 to +38
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

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

Comment on lines +33 to +34
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

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

Comment on lines +34 to +35
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

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

Comment on lines +35 to +36
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

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

Comment on lines +30 to +31
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

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

Comment on lines +38 to +39
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

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

Comment on lines +36 to +37
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
"vitest": "npm:@voidzero-dev/vite-plus-test@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

Consider adding vite-plus to the overrides section here as well to ensure version consistency across the dependency tree for this widget.

      "vite": "npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.7",
      "vite-plus": "0.1.21-alpha.7",
      "vitest": "npm:@voidzero-dev/vite-plus-test@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