Repository navigation
chore(deps): upgrade vite-plus to 1.1.0 - #3302
Conversation
Thanks for opening this pull request! 🎉We really appreciate you taking the time to contribute, @fengmk2. A maintainer will take a look as soon as they can. In the meantime, please make sure that:
If anything needs adjusting we'll leave comments here. Thanks again! |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Summary
Priority: ⬇️ Low Merge Risk: ⚪ Minimal · up to A Nuxt dependency advertises a Vite peer range that excludes the selected alias, but no resulting build or test failure is established. The tooling changes have minimal demonstrated merge risk. Pre-merge checks |
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
📊 Dependency Size ChangesWarning This PR adds 1.8 MB of new dependencies, which exceeds the threshold of 200 kB.
Total size change: 1.8 MB |
470ccb1 to
7942511
Compare
|
let me fix it |
7942511 to
69f5bef
Compare
|
@serhalp done |
Upgrade
vite-plusfrom0.3.3to1.1.0and the Vitest packages to5.0.3. Update the workspace catalog, dependency overrides, and lockfile for the new packages.The Nuxt browser project uses the browser build of
@vue/compiler-domto avoid mixed browser and CommonJS compiler code. This works around vitest-dev/vitest#11177. The configuration comment explains when to remove the alias.The test projects use Vitest
5defaults. The existing connector packaging options stay unchanged. Ignore generated.vitest/artifacts.