Skip to content

chore: upgrade vite-plus to 0.1.20-alpha.4#2

Draft
fengmk2 wants to merge 1 commit into
mainfrom
update-vite-plus-alpha-0.1.20-alpha.4
Draft

chore: upgrade vite-plus to 0.1.20-alpha.4#2
fengmk2 wants to merge 1 commit into
mainfrom
update-vite-plus-alpha-0.1.20-alpha.4

Conversation

@fengmk2

@fengmk2 fengmk2 commented Apr 28, 2026

Copy link
Copy Markdown
Owner

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

@fengmk2 fengmk2 self-assigned this Apr 28, 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 dependency to version 0.1.20-alpha.4 and refreshes the lockfile with updated versions for several packages, including oxc, oxfmt, and oxlint. Feedback identifies a critical corruption in pnpm-lock.yaml where the postcss entry is missing its header, and a version mismatch for @vitest/coverage-v8 peer dependencies that requires a catalog update in pnpm-workspace.yaml.

I am having trouble creating individual review comments. Click here to see my feedback.

pnpm-lock.yaml (3363-3365)

critical

The pnpm-lock.yaml file appears to be corrupted in the packages section. While postcss@8.5.9 was removed, its replacement postcss@8.5.10 (referenced in snapshots like line 5267) is missing its package name header, leaving an orphaned resolution block at line 3360 in the resulting file. This will cause installation failures. Please regenerate the lockfile using pnpm install to ensure consistency.

pnpm-lock.yaml (2124-2126)

medium

The peer dependency requirement for @vitest/coverage-v8 in @voidzero-dev/vite-plus-test has been updated to 4.1.5. However, the project is still resolving to 4.1.4 in the snapshots (e.g., line 5294), which creates a version mismatch. This is likely because the testing catalog in pnpm-workspace.yaml still specifies ^4.1.4. Consider updating the catalog to ^4.1.5 to maintain compatibility and avoid peer dependency warnings.

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