-
Notifications
You must be signed in to change notification settings - Fork 457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): upgrade vite
to v6
#7995
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
|
No changes to documentation |
Component Testing Report Updated Jan 16, 2025 5:24 PM (UTC) ❌ Failed Tests (2) -- expand for details
|
⚡️ Editor Performance ReportUpdated Thu, 16 Jan 2025 17:30:11 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
647ee30
to
cb4738d
Compare
cb4738d
to
8ccdff6
Compare
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a license policy violation?This package is not allowed per your license policy. Review the package's license to ensure compliance. Find a package that does not violate your license policy or adjust your policy to allow this package's license. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this, @rexxars! <3
8ccdff6
to
53c8612
Compare
vite
to v6vite
to v6, vitest
to v3
53c8612
to
3f128c4
Compare
vite
to v6, vitest
to v3vite
to v6
Description
Upgrades vite to the latest version (v6), as well as vitest to v3
What to review
Give it a test, see how it feels! Does anything break?
There's a prerelease you can use to test it on a local studio, under the
upgrade-vite-v6
branch on npm.Testing
Commands involved:
sanity dev
sanity build
sanity preview
Notes for release