Skip to content

chore: update vite-plus and related packages to 0.1.15-alpha.1#5

Draft
fengmk2 wants to merge 2 commits into
mainfrom
update-vp-to-latest
Draft

chore: update vite-plus and related packages to 0.1.15-alpha.1#5
fengmk2 wants to merge 2 commits into
mainfrom
update-vp-to-latest

Conversation

@fengmk2
Copy link
Copy Markdown
Owner

@fengmk2 fengmk2 commented Mar 27, 2026

🔗 Linked issue

🧭 Context

📚 Description

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 introduces a new pre-commit hook and updates several dependencies, including vite-plus, vite, and vitest, to an alpha version (0.1.15-alpha.1). The review feedback emphasizes the risks associated with using pre-release versions for core build and testing tools, which could lead to instability across the workspace. Additionally, it is suggested that vite-plus be moved to devDependencies to better reflect its role as a development tool.

Comment thread package.json
"virtua": "0.48.8",
"vite-plugin-pwa": "1.2.0",
"vite-plus": "0.1.12",
"vite-plus": "0.1.15-alpha.1",
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

Using a pre-release version (0.1.15-alpha.1) for vite-plus can introduce instability. It is recommended to use stable releases. Additionally, since vite-plus appears to be a development tool, it should be moved to devDependencies.

Comment thread pnpm-workspace.yaml
sharp: 0.34.5
vite: npm:@voidzero-dev/vite-plus-core@0.1.12
vitest: npm:@voidzero-dev/vite-plus-test@0.1.12
vite: npm:@voidzero-dev/vite-plus-core@0.1.15-alpha.1
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

Overriding vite to an alpha version (0.1.15-alpha.1) workspace-wide is risky. Pre-release versions can be unstable and may break the build process for all packages in the workspace. It is strongly recommended to use a stable version of vite to ensure reliability.

Comment thread package.json
"typescript": "6.0.2",
"unplugin-vue-markdown": "30.0.0",
"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.12",
"vitest": "npm:@voidzero-dev/vite-plus-test@0.1.15-alpha.1",
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

Using an alpha version (0.1.15-alpha.1) for vitest can introduce instability to the testing workflow. It is advisable to use stable versions to ensure CI/CD and local development are not disrupted by potential bugs in the pre-release.

Comment thread pnpm-workspace.yaml
vite: npm:@voidzero-dev/vite-plus-core@0.1.12
vitest: npm:@voidzero-dev/vite-plus-test@0.1.12
vite: npm:@voidzero-dev/vite-plus-core@0.1.15-alpha.1
vitest: npm:@voidzero-dev/vite-plus-test@0.1.15-alpha.1
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

Overriding vitest to an alpha version (0.1.15-alpha.1) across the workspace can lead to an unstable testing environment. To maintain a reliable testing pipeline, it is recommended to use stable releases.

@autofix-troubleshooter
Copy link
Copy Markdown

Hi! I'm the autofix logoautofix.ci troubleshooter bot.

It looks like you correctly set up a CI job that uses the autofix.ci GitHub Action, but the autofix.ci GitHub App has not been installed for this repository. This means that autofix.ci unfortunately does not have the permissions to fix this pull request. If you are the repository owner, please install the app and then restart the CI workflow! 😃

@github-actions github-actions Bot added stale and removed stale labels Apr 29, 2026
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.

2 participants