chore: upgrade vite-plus to 0.1.20-alpha.4#2
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the vite-plus dependency to version 0.1.20-alpha.4 across multiple packages and updates the pnpm-lock.yaml file accordingly. I have identified that the packages/e2e/package.json file is missing the corresponding update for vite-plus, which should be addressed to ensure workspace consistency. Additionally, I recommend pinning the detox dependency to a specific version in package.json instead of using the latest tag to improve build reproducibility.
| vite-plus: | ||
| specifier: latest | ||
| version: 0.1.15(@types/node@20.19.34)(esbuild@0.27.4)(happy-dom@15.11.7)(jiti@2.6.1)(publint@0.3.18)(terser@5.46.0)(tsx@4.21.0)(typescript@5.9.3)(vite@6.4.1(@types/node@20.19.34)(jiti@2.6.1)(lightningcss@1.31.1)(terser@5.46.0)(tsx@4.21.0)(yaml@2.8.2))(yaml@2.8.2) | ||
| specifier: 0.1.20-alpha.4 |
There was a problem hiding this comment.
| detox: | ||
| specifier: latest | ||
| version: 20.50.1(@jest/environment@30.3.0)(@jest/types@30.3.0)(expect@30.3.0)(jest-environment-node@30.3.0)(jest@30.3.0(@types/node@20.19.34)) | ||
| version: 20.51.0(@jest/environment@30.3.0)(@jest/types@30.3.0)(expect@30.3.0)(jest-environment-node@30.3.0)(jest@30.3.0(@types/node@20.19.34)) |
There was a problem hiding this comment.
The detox dependency in packages/e2e is currently using the latest tag (as seen in the specifier on line 91), which led to an automatic version bump from 20.50.1 to 20.51.0 in this lockfile update. It is recommended to pin dependencies to specific versions in package.json to ensure build reproducibility and avoid unexpected breaking changes.
commit: |
Upgrade vite-plus and related packages to 0.1.20-alpha.4 alpha version.