chore: upgrade vite-plus to 0.1.21-alpha.4#11
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 streamlines the AGENTS.md documentation by removing detailed workflow sections and common pitfalls, replacing them with links to the official documentation and a simplified review checklist. It also updates vite, vite-plus, and vitest to version 0.1.21-alpha.4 in the pnpm-workspace.yaml file. A review comment suggests caution when upgrading to alpha versions due to potential instability and breaking changes.
| vite: npm:@voidzero-dev/vite-plus-core@0.1.21-alpha.4 | ||
| vite-plugin-commonjs: ^0.10.4 | ||
| vite-plus: 0.1.17 | ||
| vite-plus: 0.1.21-alpha.4 |
There was a problem hiding this comment.
Upgrading vite-plus and its related packages to an alpha version (0.1.21-alpha.4) introduces a risk of instability. Alpha releases are not feature-complete and may contain bugs or undergo breaking changes before a stable release. For production environments or long-term stability, it is advisable to use stable versions.
- Remove unused PHASE_PRODUCTION_BUILD import in next-config.ts (re-exported directly from shims/constants instead) - Remove unused patternToNextFormat import in pages-router.ts (re-exported directly from route-validation.js instead) - Update oxlint-disable comment in fixtures.ts to use the correct rule name (react-hooks/rules-of-hooks) and place it on the actual hook call site
'unknown' already includes undefined, so the union is redundant. oxlint in vite-plus 0.1.21-alpha.4 now treats warnings as CI failures.
1 participant
Upgrade vite-plus and related packages to 0.1.21-alpha.4 alpha version.