chore(deps): bump vite-plus to 0.1.21-alpha.7#3
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates several package.json files to pin the versions of @voidzero-dev/vite-plus-core, @voidzero-dev/vite-plus-test, and vite-plus to 0.1.21-alpha.7. A review comment suggests using version ranges (e.g., >=0.1.21-alpha.7) instead of hard-pinned versions for peerDependencies to improve compatibility and maintain consistency with other dependency definitions in the project.
| "@voidzero-dev/vite-plus-core": "0.1.21-alpha.7", | ||
| "@voidzero-dev/vite-plus-test": "0.1.21-alpha.7", | ||
| "jsdom": "*", | ||
| "typescript": "*", | ||
| "vite-plus": "*" | ||
| "vite-plus": "0.1.21-alpha.7" |
There was a problem hiding this comment.
For peerDependencies, it is generally recommended to use a version range (e.g., >=0.1.21-alpha.7) rather than a hard-pinned version. This provides better compatibility for consumers of the package and avoids potential version conflicts when minor updates or bug fixes are released in subsequent alpha versions. This would also be consistent with how other peer dependencies like @faasjs/core are defined in this file.
| "@voidzero-dev/vite-plus-core": "0.1.21-alpha.7", | |
| "@voidzero-dev/vite-plus-test": "0.1.21-alpha.7", | |
| "jsdom": "*", | |
| "typescript": "*", | |
| "vite-plus": "*" | |
| "vite-plus": "0.1.21-alpha.7" | |
| "@voidzero-dev/vite-plus-core": ">=0.1.21-alpha.7", | |
| "@voidzero-dev/vite-plus-test": ">=0.1.21-alpha.7", | |
| "jsdom": "*", | |
| "typescript": "*", | |
| "vite-plus": ">=0.1.21-alpha.7" |
Summary
Bump
vite-plusand related packages to alpha 0.1.21-alpha.7.Updated where applicable:
vite-plusvitest(alias to@voidzero-dev/vite-plus-test)vite(alias to@voidzero-dev/vite-plus-core)overrides/resolutions/pnpm.overrides/pnpm-workspace.yamlcatalogsminimumReleaseAgeExclude/minimumReleaseAgeExcludesconfigured for pnpm + bunTest plan