Vitest 5 is here! 🎉
- Big performance improvements (vm pools up to 53% faster, ~18% boost across the board including Browser Mode)
- New builtin Trace View in Browser Mode
- Nested projects support
- New benchmarking API
- New `vi.when` API
- Better defaults
- And a lot of bug fixes!
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
🚨 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
Vitest 4.1 is out! 🚀
✅ 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
Just deleted a bunch of testing boilerplate in this repo after @vitest added `import.meta.resolve` support 🏆
So happy with @vitest Browser Mode being stable! Migrated legacy Jest component tests that used jsdom, tested implementation details, and mocked web components. Now: reliable user-facing tests with getBy* locators, no mocking, running in a real browser. Tests what users actually see and do 🎉
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
Vitest Browser Mode now almost 1.2 million weekly downloads 😮
Vitest 3.2 is out!
- New Annotations API
- Scoped Fixtures
- Custom Browser Locators API
- Test Signal
- Better V8 Coverage Result
And many more features!
@vite @chaosexanima We also migrated from Jest to @vitest, and removed 30% of our (indirect) Javascript package dependencies
@zachleat And it's pretty smart about only re-running the tests for the changes you made. Even when running under debugger, it's almost as fast as I type.
Really enjoying working with https://vitest.dev/ on a project that needs to be tested in Node, Safari, Firefox, and Chrome!
My favorite bits:
1. Easy to setup headless browsers with Browser Mode
2. CLI runs in watch mode by default (and not on CI)
3. Has all the `assert` APIs I was used to
4. test.skipIf 🏆
5. `only` works without modifying the CLI command (I know why Node test runner does this but it’s proven more annoying than helpful)
Give us your thoughts on the benchmarking feature in Vitest ⚡️
Milestone: vitest crossed 10M weekly npm downloads! ⚡
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.
We published a CVE for a moderate dev server security vulnerability. Please update to the latest versions: 6.2.4, 6.1.3, 6.0.13, 5.4.16, 4.5.11.
https://github.com/vitejs/vite/security/advisories/GHSA-4r4m-qw57-chr8
Vitest 3.1.0: hide output from passing tests and more
@vitest
https://github.com/vitest-dev/vitest/releases/tag/v3.1.0
Vite 6.1 is out! The 7.5K commits to main release ⚡
https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md#610-2025-02-05