Use Vitest for snaps-execution-environments browser tests

[Mrtenz]

Proof of concept for using Vitest for browser tests.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@vitest/coverage-istanbul@3.0.8	None	0	13.7 kB	vitestbot
npm/istanbul-lib-coverage@3.2.0 ➜ 3.2.2	None	0	34.4 kB	oss-bot
npm/istanbul-lib-report@3.0.0 ➜ 3.0.1	None	0	37.6 kB	oss-bot
npm/istanbul-reports@3.1.5 ➜ 3.1.7	None	0	294 kB	oss-bot
npm/make-dir@3.1.0 ➜ 4.0.0	None	0	9.91 kB	sindresorhus
npm/playwright-core@1.51.0	None	0	0 B
npm/playwright@1.51.0	None	0	3.21 MB	dgozman, dgozman-ms, pavelfeldman, ...1 more

🚮 Removed packages: npm/@babel/helper-string-parser@7.23.4, npm/@babel/parser@7.23.9, npm/@jridgewell/gen-mapping@0.3.3, npm/@jridgewell/set-array@1.1.2, npm/jackspeak@2.3.6, npm/lru-cache@10.1.0, npm/magic-string@0.30.3, npm/path-scurry@1.10.1, npm/postcss@8.4.31, npm/source-map-js@1.0.2

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
New author	npm/istanbul-lib-report@3.0.1	New Author: oss-bot Previous Author: coreyfarrell	packages/snaps-controllers/package.json packages/snaps-execution-environments/package.json packages/snaps-utils/package.json yarn.lock	🚫

View full report↗︎

Next steps

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

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/istanbul-lib-report@3.0.1