I have cancelled my GitHub Sponsors account today. If you've been sponsoring me before, consider redirecting the funds to Vitest directly 💚

Interested in the story behind @voidzero.dev joining @cloudflare.social? So was I! Luckily @evanyou.me, Founder & CEO of VoidZero, creator of @vuejs.org & @vite.dev, & now part of Cloudflare's #oss team, joined me to discuss. 👉 redmonk.com/videos/evan-... @redmonk.com youtube.com/shorts/98v0t...

Get first access to our @vitest.dev plugin, which adds Chromatic’s visual testing and review to your browser tests. It’s built by @ariperkkio.dev, a Vitest core maintainer. It’s free to use while in beta and requires no changes to your test files. Read on for more info 🧵

🌌 Tales from the Void: Our May 2026 Recap Don't miss out on the news: 🧡 VoidZero is now part of Cloudflare ⚡ Rolldown got its first stable release 🔒 Vite security patches 🧪 Vitest going engine-agnostic 🦀 Oxfmt up to 25% faster 👀 and more from the community Full recap 👇 voidzero.dev/posts/whats-...

VoidZero, the team behind Vite, Vitest, Rolldown, Oxc, and Vite+, is joining Cloudflare. Vite stays open source, vendor-agnostic, and built for everyone. https://cfl.re/4dR0LYA

VoidZero is joining Cloudflare. Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.

Today, VoidZero joins Cloudflare. Vite remains MIT, vendor-neutral, and stewarded by the same wider team. The same goes for Vitest, Rolldown, and Oxc. Cloudflare is also committing $1M to an OSS fund to support independent development in the Vite ecosystem.

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 github.com/vitest-dev/v...

Building this integration has been amazing opportunity to dogfood all APIs we've added into @vitest.dev in past years. It's using features like new Reporter APIs, Vitest plugin hooks, browser commands, CDP, test tags and much more! Vitest is definitely one of the most extensible JS tools out there.

We’re launching early access for Vitest visual testing with Chromatic! ⚡️ Built with @vitest.dev core maintainer ariperkkio.dev, Chromatic adds visual testing to the browser tests you already write. 🧵 (1/4)

🦸 The legends who stayed till the very end of yesterday's #ReactSummit Pragmatic Testing workshop. I love how @vitest.dev + a resilient testing strategy makes tests look the same across frameworks.

🚨 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 github.com/vitest-dev/v... for more information

Couldn't keep up with all the news? We got some selected highlight from last month to recap! 🌀 → Vite Plus lazyPlugins API → @vitest.dev 5 sneak peak → Oxlint: RFC for linting Svelte/Vue/Angular templates → Module Federation in @vite.dev via plugin → @npmx.dev vp option youtu.be/zwY4UZr-qjc

🫡 Bye `fakeAsync`, thanks for your service. ✨ Angular 22 will ship an option to migrate `fakeAsync` to @vitest.dev fake timers 🗑️ No more Zone.js patching just because of `fakeAsync` 🙏 Thanks to Andrew Scott and Charles Lyding for welcoming the idea and for the feedback github.com/angular/angu...

Tales from the Void: April 2026 is out! ✨ This month at VoidZero: ◇ Our approach to supply chain security & trusted publishing ◇ A new Oxc-based Angular Compiler that is up 20x faster ◇ Vite+ `lazyPlugin` to reduce slowdowns ◇ @vitest.dev Browser Mode trace viewer ◇ @rolldown.rs module tags

@vitest.dev is going framework agnostic, and we need your feedback!

Take a first look at the new @vitest.dev Browser Mode's trace viewer 👀 Design is not final 😄 Thank you, @hiogawa.bsky.social for working on it! main.vitest.dev/guide/browse...

what are these downloads numbers 🤨

Did you know that @vitest.dev has an Agent reporter? 🤖 Instead of outputting all the details, it ensures only the failing tests and summary are sent to your agent. That means less tokens used and less information overload. Since Vitest 4.1 this is the default when detecting an agent.

There's some impressive work going on with 3rd party oxc powered coverage instrumentation that can replace Babel based istanbul-lib-instrument 👀 > 8-11x faster than babel-plugin-istanbul, 13-15x faster than swc-plugin-coverage-instrument (Rust/WASM), 25-30x faster than istanbul-lib-instrument.

Really enjoying the Storybook/Vitest integration and the accessibility addon. It's friction at its best; easily detect an issue, serve you a direct link to the documentation about the rule so you learn something as a developer + the details you need to go fix it immediately 👏

vitest no longer supporting node 18 has been a good way to get a huge number of projects to bump their minimum node version 😄

Want to start writing tests but no idea how to get started? The @vitest.dev docs now have a Learn section that covers evergreen concepts (matchers, tests, dealing with async code, mocks, ...) and also current topics like writing good tests with AI! Time to get started 🎉

@vitest.dev now has a new `--experimental.preParse` flag to avoid running all test files when you apply filters. For example, if you have `.only` tests or use `-t` or `--tags-filters` Vitest will now only run matching test files. Try it now! vitest.dev/config/exper...

Did you know that @vitest.dev UI shows you slow tests since 4.1? No more scrolling to find them! Do you use Vitest UI or rather prefer the terminal output?

👏 @analogjs.org 2.4 for @angular.dev is out! ⚡️ Support for @vite.dev 8 w/Rolldown 🧪 Enhanced testing DX with @vitest.dev 🧑‍🚀 Improved integration with @astro.build And more! 👇 dev.to/analogjs/ana...

🖇️ Our latest release of @fast-check/vitest added native support for before each/afterEach hooks of @vitest.dev. No more need to manually connect them into fast-check assertions they get automatically integrated if you use our connector package. Connector: npmx.dev/package/@fas...

🫣

👁️ the @vitest.dev addon for @storybook.js.org has almost 2 million weekly downloads and I'm only discovering it now? package: npmx.dev/package/@sto... docs: storybook.js.org/docs/writing...

Join the Vite ecosystem tomorrow to celebrate the Vite Team 5th Anniversary by rewatching together the Vite Documentary! Let's remember the stories of the people who connected to extend together our shared commons. And stay at 3:45 PM UTC to participate in the live stage after the movie 💜

This day 4 years ago I sent my first PR to @vitest.dev. Back then it was on v0.7.4 with 80K weekly downloads. After one year and +70 more PRs, @antfu.me and @erus.dev invited me to join the team. Today we are at v4.1.0 with 35M weekly downloads. Maybe in 2030 we'll have Vitest 8 with 140M downloads.

Debounces, delays, intervals... they either break your tests or slow them down. ⏩ Since @vitest.dev 4.1.0, you can now "fast-forward" time in your tests with `nextTimerAsync` tick mode. ❤️ credit goes to Andrew Scott (@angular.dev team) 🧑‍🍳 recipe → cookbook.marmicode.io/angular/test...

I just need a few more of you to migrate to @vitest.dev so I can prove that crystal balls work 🔮 😉 (the charts from npmx.dev are so neat ❤️)

Vite and Vitest have been a pleasure to use in my oss projects since switching to them. Kudos to those teams.

Async leak detection in action - caught a missing gcTime: Infinity in our TanStack Query test setup in one of our projects.

Announcing Vite+ Alpha. Now open source. To make JavaScript developers more productive than ever before. A single binary that: ◆ Unifies your frontend toolchain ◆ Manages your runtime & pkg manager ◆ Caching & monorepo support Works with every framework and meta framework in the Vite ecosystem.

Very excited about this update! Tons of new stuff coming 🎉

⚡️ Vite 8.0 is here! The most significant architectural change since Vite 2. ⏬ Powered by @rolldown.rs bringing faster production builds and more consistency 🛤️ New features such as tsconfig paths and emitDecoratorMetadata support vite.dev/blog/announc...

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 vitest.dev/blog/vitest-...

We're joining with the Vite team to re-premiere our Vite documentary!⚡️ 📅 Happening 19th March at 4pm CET | 10am CST 📺 Screening on the Vite website 💬 Followed by a live stage on Discord with Vite devs from the film Come hang out!

@vitest.dev vscode extension now supports @deno.land!

Been recently really enjoying working with Vitest tbh (both for client’s design system and also for my personal projects). I’m just nerding out over the terminal colors at this point tho

🧪 In the latest release of @analogjs.org, you can migrate to @vitest.dev with browser mode for @playwright.dev enabled and automatically configured using an @angular.dev schematic! analogjs.org/docs/feature...

✨ What's New in ViteLand: February 2026 Recap ◆ Oxfmt Beta: 100% Prettier conformance ◆ @vite.dev 8 includes devtools ◆ @vitest.dev 4.1 beta adds aroundEach/aroundAll hooks ◆ @rolldown.rs becomes 9.6% faster ◆ Oxlint now supports 59/61 ts-eslint rules ◆ NestJS migrates to Vitest ◆ and much more 👀

4 new packages added to Awesome Vitest in the last 7 days: 1 reporter, 2 utilities, and 1 browser mode environment. The ecosystem keeps growing. Building tooling for @vitest.dev? PRs are welcome!

This is my favorite kind of changes. Experimental runners out, clarity in. @vitest.dev is the path. Thanks Alan! github.com/angular/angu...

I started a collection of resources for @vitest.dev + Svelte / SvelteKit testing. If you know a good learning resource (also Vitest in general), please let me know. fubits.dev/notes/2026-0...

The fact that Vitest can run 1k tests in just 164 ms is mind-blowing.

Flaky tests and memory leaks are the worst. @vitest.dev now has a flag that catches uncleared intervals, lingering servers, and other async operations leaking across your tests. Available in the latest 4.1 beta. Big shout out to @ariperkkio.dev from the Vitest team for landing this PR! 🔥

Vitest 4.1 is on the horizon, but we're already looking ahead! What are your main pain points in your testing workflow right now? Let us know in the Vitest 5 discussion thread!