chore: upgrade vite-plus to 0.1.20-alpha.4#1
Conversation
There was a problem hiding this comment.
Code Review
This pull request pins the versions of vite-plus, vite, and vitest to a specific alpha release (0.1.20-alpha.4) across multiple package.json files. A review comment suggests using a version range for the peerDependency in packages/dev/package.json to prevent potential dependency conflicts and allow for compatible updates.
| "jsdom": "*", | ||
| "typescript": "*", | ||
| "vite-plus": "*" | ||
| "vite-plus": "0.1.20-alpha.4" |
There was a problem hiding this comment.
Pinning a peerDependency to an exact alpha version is very restrictive and can lead to dependency conflicts for consumers of this package. Since other peer dependencies in this file use version ranges (e.g., >=8.0.0-beta.26), consider using a range here as well to allow for compatible updates of vite-plus without requiring a new release of @faasjs/dev.
| "vite-plus": "0.1.20-alpha.4" | |
| "vite-plus": ">=0.1.20-alpha.4" |
Upgrade vite-plus and related packages to 0.1.20-alpha.4 alpha version.