✅ Vite 8 support from day 1
🏷️ Test tags to organize, filter & apply shared options
🪝 New hooks for easier tracing, transactions and AsyncLocalStorage
🔍 Async leak detection
🤖 Agent reporter to reduce token usage

And much more!

Full blog post at https://vitest.dev/blog/vitest-4-1.html

vitest.dev

Announcing Vitest 4.1

Vitest 4.1 Release Announcement

Vitest @vitest@m.webtoo.ls

· 11mo ago

Vitest 4 is out!

🎊 Browser Mode is Stable
👀 Visual Regression Testing
🛠️ Improved Debugging
⛵️ Pool Stabilization
✨ New APIs
✅ Bug Fixes

Stay updated with our blog post: https://vitest.dev/blog/vitest-4

#testing #javascript #vitest #vite

vitest.dev

Announcing Vitest 4.0

Vitest 4.0 Release Announcement

Vitest @vitest@m.webtoo.ls

· 4mo ago

🚨 We are publishing Vitest 4.1.6 and Vitest 5.0.0-beta.3 to resolve recent vulnerabilities:

- `--api` and `--ui` exposed arbitrary files to the network
- `--api` allowed arbitrary execution
- `?otelCarrier` XSS

Check https://github.com/vitest-dev/vitest/security for more information

GitHub

Build software better, together

GitHub is where people build software. More than 225 million people use GitHub to discover, fork, and contribute to over 800 million projects.

Vitest @vitest@m.webtoo.ls

· 4mo ago

We've published a Browser Mode security advisory.

CDP-capable providers like Playwright Chromium with the browser API exposed to the network allowed attackers to run code on the host.

Update vitest/browser to 5.0.0-beta.4, 4.1.8, or 3.2.6.
Vite+ users: Upgrade to 0.1.24

https://github.com/vitest-dev/vitest/security/advisories/GHSA-g8mr-85jm-7xhm

GitHub

Exposed Browser Mode API Can Proxy CDP and Overwrite Config Files, Leading to RCE

## Summary Vitest Browser Mode exposes a `cdp()` API that forwards raw Chrome DevTools Protocol (CDP) methods over the Vitest browser WebSocket RPC. CDP is not gated by `browser.api.allowWrite`,...

Vitest @vitest@m.webtoo.ls

· 16mo ago

Vitest 3.2 is out!
- New Annotations API
- Scoped Fixtures
- Custom Browser Locators API
- Test Signal
- Better V8 Coverage Result
And many more features!

https://vitest.dev/blog/vitest-3-2.html

#webdev #testing #javascript #typescript

vitest.dev

Announcing Vitest 3.2

Vitest 3.2 Release Announcement

Vitest @vitest@m.webtoo.ls

· 18mo ago

Milestone: vitest crossed 10M weekly npm downloads! ⚡

Vitest @vitest@m.webtoo.ls

· 22mo ago

We're looking for a good folk from the Vitest community to help us with our social presence in Mastodon. Please comment here if you're interested or join our discord server.

Vitest @vitest@m.webtoo.ls

· 18mo ago

Vitest 3.1.0 is out! ⚡

Apart from performance improvements and fixes, this release expands your test setup flexibility with new options. Check out the release notes here.

👉 https://github.com/vitest-dev/vitest/releases/tag/v3.1.0

GitHub

Release v3.1.0 · vitest-dev/vitest

🚀 Features Introduce %$ option to add number of the test to its title - by @kemuridama in #7412 (df347) Add diff.maxDepth option and set non-Infinity value as a default to reduce crash - by @hi-og...

Vitest @vitest@m.webtoo.ls

· 24mo ago

What happens when Storybook and Vitest are mashed together?
https://youtu.be/8t5wxrFpCQY

Yann Braga | Component Testing with Storybook and Vitest | ViteConf 2024

Vitest @vitest@m.webtoo.ls

· 14mo ago

Vitest Browser Mode now almost 1.2 million weekly downloads 😮

Vitest @vitest@m.webtoo.ls

· 20mo ago

Replying to

The patched versions also include patches for a browser mode security vulnerability. https://github.com/vitest-dev/vitest/security/advisories/GHSA-8gvc-j273-4wm5

GitHub

Browser mode serves arbitrary files

### Summary `__screenshot-error` handler on the browser mode HTTP server that responds any file on the file system. Especially if the server is exposed on the network by [`browser.api.host: true`]...

Vitest @vitest@m.webtoo.ls

· 17mo ago

Give us your thoughts on the benchmarking feature in Vitest ⚡️

👉 https://github.com/vitest-dev/vitest/discussions/7850

#webdev #testing

GitHub

Benchmarking Support · vitest-dev vitest · Discussion #7850

Vitest provides an experimental support for benchmarking for quite a while now. So far, the feature is still kept as experimental because we identified several issues that we think should be resolv...