chore(deps): bump vite-plus to v0.2.0#8
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds release age configurations and updates catalog dependencies in pnpm-workspace.yaml. Feedback highlights that the added release age settings are .npmrc configurations and will be ignored in pnpm-workspace.yaml. Additionally, the reviewer suggests correcting the pkg.pr.new URL path for vite-plus to avoid resolution issues, and adding @vitest/coverage-v8 to the catalog to prevent version mismatches with vitest.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| minimumReleaseAge: 60 | ||
| minimumReleaseAgeExclude: | ||
| - '@voidzero-dev/*' | ||
| - vite-plus | ||
| - '@vitest/*' | ||
| - vite | ||
| - vitest | ||
| - '@oxc-project/*' | ||
| - '@oxlint/*' | ||
| - oxlint | ||
| - oxfmt | ||
| - oxlint-tsgolint | ||
| blockExoticSubdeps: false | ||
|
|
There was a problem hiding this comment.
These configuration options (minimumReleaseAge, minimumReleaseAgeExclude, and blockExoticSubdeps) are .npmrc settings and are not supported in pnpm-workspace.yaml. Placing them here will cause pnpm to silently ignore them.
To fix this, they should be moved to the .npmrc file at the root of your workspace using kebab-case:
minimum-release-age=60
minimum-release-age-exclude[]=@voidzero-dev/*
minimum-release-age-exclude[]=vite-plus
minimum-release-age-exclude[]=@vitest/*
minimum-release-age-exclude[]=vite
minimum-release-age-exclude[]=vitest
minimum-release-age-exclude[]=@oxc-project/*
minimum-release-age-exclude[]=@oxlint/*
minimum-release-age-exclude[]=oxlint
minimum-release-age-exclude[]=oxfmt
minimum-release-age-exclude[]=oxlint-tsgolint
block-exotic-subdeps=false| vite-plus: 0.1.24 | ||
| vitest: npm:@voidzero-dev/vite-plus-test@0.1.24 | ||
| vite: 'https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856' | ||
| vite-plus: 'https://pkg.pr.new/voidzero-dev/vite-plus@1856' |
There was a problem hiding this comment.
Since vite-plus is a monorepo, the pkg.pr.new URL should explicitly include the package name in the path, similar to how @voidzero-dev/vite-plus-core is defined. Omitting it may cause resolution issues during installation.
vite-plus: 'https://pkg.pr.new/voidzero-dev/vite-plus/vite-plus@1856'| vitest: npm:@voidzero-dev/vite-plus-test@0.1.24 | ||
| vite: 'https://pkg.pr.new/voidzero-dev/vite-plus/@voidzero-dev/vite-plus-core@1856' | ||
| vite-plus: 'https://pkg.pr.new/voidzero-dev/vite-plus@1856' | ||
| vitest: '4.1.9' |
There was a problem hiding this comment.
The vitest package is updated to 4.1.9 here, but @vitest/coverage-v8 in package.json is still at 4.1.8. To prevent version mismatch issues, consider adding @vitest/coverage-v8 to the catalog as well so both can be kept in sync.
vitest: '4.1.9'
'@vitest/coverage-v8': '4.1.9'
cf-fate
create-fate
@nkzw/fate
react-fate
void-fate
vue-fate
commit: |
1 participant
Summary
Bump
vite-plusand related packages to the pkg.pr.new prerelease build for v0.2.0.Updated where applicable:
vite-plus-> pkg.pr.new buildvite(alias/override ->@voidzero-dev/vite-plus-core)vitestpinned to bundled4.1.9(the@voidzero-dev/vite-plus-testwrapper was removed upstream; vitest is now plain upstream)@vitest/browser-playwrightadded (4.1.9) since the browser provider is now an optional peer dep used byvite.config.tsminimumReleaseAgeenabled with vite-plus packages excluded (pnpm/bun/npm as applicable)Test plan