chore: upgrade vite-plus to 0.1.19-alpha.3#1
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 updates the vite-plus dependency to version 0.1.19-alpha.3 in the template and workspace catalog, which results in corresponding updates to related packages like oxlint-tsgolint and @oxc-project tools in the lockfile. The reviewer recommends using caret ranges instead of pinned versions for the new alpha release to maintain consistency with other pre-release dependencies and to ensure that users receive subsequent bug fixes automatically.
| "@typescript/native-preview": "^7.0.0-dev.20260420.1", | ||
| "tailwindcss": "^4.2.3", | ||
| "vite-plus": "^0.1.18" | ||
| "vite-plus": "0.1.19-alpha.3" |
There was a problem hiding this comment.
The vite-plus dependency is pinned to a specific alpha version, which is inconsistent with other dependencies in this template (like @typescript/native-preview) and the previous configuration that used a caret range. Using a caret range like ^0.1.19-alpha.3 is generally preferred for pre-release versions to allow automatic updates to subsequent alpha/beta releases within the same minor version, ensuring users of the template receive bug fixes.
| "vite-plus": "0.1.19-alpha.3" | |
| "vite-plus": "^0.1.19-alpha.3" |
| rolldown: ^1.0.0-rc.16 | ||
| vite: ^8.0.9 | ||
| vite-plus: ^0.1.18 | ||
| vite-plus: 0.1.19-alpha.3 |
There was a problem hiding this comment.
The vite-plus version in the build catalog is pinned, while other pre-release dependencies in the same catalog, such as rolldown, use a caret range (^1.0.0-rc.16). For consistency and to ensure the workspace benefits from future alpha updates within the same minor range, it is recommended to use a caret range.
vite-plus: ^0.1.19-alpha.31 participant
Upgrade vite-plus and related packages to 0.1.19-alpha.3 alpha version.