Skip to content

chore: upgrade vite-plus to 0.1.16-alpha.4#3

Draft
fengmk2 wants to merge 1 commit into
masterfrom
update-vite-plus-alpha-0.1.16-alpha.4
Draft

chore: upgrade vite-plus to 0.1.16-alpha.4#3
fengmk2 wants to merge 1 commit into
masterfrom
update-vite-plus-alpha-0.1.16-alpha.4

Conversation

@fengmk2

@fengmk2 fengmk2 commented Apr 6, 2026

Copy link
Copy Markdown
Owner

Upgrade vite-plus and related packages to 0.1.16-alpha.4 alpha version.

@fengmk2 fengmk2 self-assigned this Apr 6, 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 vite, vite-plus, and vitest to a pinned alpha version (0.1.16-alpha.4) and synchronizes the lockfile, which includes updating several @oxc-project, @oxfmt, and @oxlint dependencies while removing esbuild and cac. Feedback suggests that using pre-release versions can introduce instability and that stable releases are generally recommended for production environments.

Comment thread package.json
Comment on lines +84 to +88
"vite": "npm:@voidzero-dev/vite-plus-core@0.1.16-alpha.4",
"vite-plus": "0.1.16-alpha.4",
"vitepress": "^1.6.3",
"vitepress-plugin-llms": "^1.11.0",
"vitest": "npm:@voidzero-dev/vite-plus-test@^0.1.11",
"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.16-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.

high

This change updates vite, vite-plus, and vitest to a pinned alpha version (0.1.16-alpha.4). While this might be intentional for testing new features, using pre-release versions can introduce instability and breaking changes. It is generally recommended to use stable releases, especially for production environments, to avoid potential risks.

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