V5: Replace jest with vitest

[vio]

No description provided.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/typescript-eslint@8.26.0	Transitive: environment, filesystem	+38	3.95 MB	jameshenry
npm/typescript@5.8.2	None	0	22.9 MB	typescript-bot
npm/verdaccio@6.0.5	environment, filesystem, network Transitive: eval, shell, unsafe	+255	29.3 MB	verdaccio.npm
npm/vitest@3.0.8	environment, eval Transitive: filesystem, network, shell, unsafe	+76	270 MB	vitestbot
npm/webpack@5.98.0	Transitive: environment, eval, filesystem, shell, unsafe	+74	17.5 MB	evilebottnawi, jhnns, sokra, ...1 more
npm/yargs@17.7.2	environment, filesystem	+11	572 kB	oss-bot

🚮 Removed packages: npm/@types/jest@29.5.14, npm/eslint-plugin-jest@28.11.0, npm/jest@29.7.0

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
License Policy Violation	npm/typescript@5.8.2	License: CC-BY-4.0 (package/ThirdPartyNoticeText.txt) License: MIT-Khronos-old (package/ThirdPartyNoticeText.txt) License: unrecognized license (package/ThirdPartyNoticeText.txt)	package-lock.json package.json	⚠︎
License Policy Violation	npm/vite@6.2.2	License: unrecognized license (package/LICENSE.md)	package-lock.json package.json	⚠︎

View full report↗︎

Next steps

What 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 dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/typescript@5.8.2
• @SocketSecurity ignore npm/vite@6.2.2