Skip to content

chore: upgrade vite-plus to 0.1.17-alpha.4#4

Draft
fengmk2 wants to merge 2 commits into
masterfrom
update-vite-plus-alpha-0.1.17-alpha.4
Draft

chore: upgrade vite-plus to 0.1.17-alpha.4#4
fengmk2 wants to merge 2 commits into
masterfrom
update-vite-plus-alpha-0.1.17-alpha.4

Conversation

@fengmk2

@fengmk2 fengmk2 commented Apr 13, 2026

Copy link
Copy Markdown
Owner

Upgrade vite-plus and related packages to 0.1.17-alpha.4

@fengmk2 fengmk2 self-assigned this Apr 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 vite-plus ecosystem and its associated dependencies to version 0.1.17-alpha.4. Feedback was provided to include vite-plus in the overrides section of package.json to ensure version consistency and prevent potential conflicts within nested dependencies.

Comment thread package.json Outdated
Comment on lines +112 to +113
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.17-alpha.4",
"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.17-alpha.4"

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 consistency and to prevent potential version conflicts in nested dependencies, it's a good practice to also include vite-plus in the overrides section, similar to vite and vitest. This ensures that all parts of your project use the same alpha version of the vite-plus ecosystem.

Since you are using an alpha version, pinning it in overrides will prevent other packages from accidentally resolving to a different version.

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

@fengmk2 fengmk2 force-pushed the update-vite-plus-alpha-0.1.17-alpha.4 branch from 3fc87d7 to e4dc693 Compare April 14, 2026 12:07
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