@vite.dev and @vitest.dev crushing the positive sentiment of devs who used it in the State of JS survey 🚀

For all your AsyncLocalStorage needs, Vitest 4.1 now supports `aroundEach` and `aroundAll` hooks! main.vitest.dev/api/hooks#ar...

✨ What's New in ViteLand: January 2026 Recap ◆ Unified redesign across all VoidZero sites ◆ @vite.dev crossed 3 billion npm downloads ◆ @rolldown.rs reached RC status ◆ Lazy Barrel Optimization landed in Rolldown ◆ Oxfmt hit 100% Prettier conformance ◆ ...and more 👀 voidzero.dev/posts/whats-...

The State of JS 2025 results are out! 🏆 Most Adopted Tech → Vitest 🏆 Highest Satisfaction → Vite (98%) & Vitest (97%) 🏆 Highest Interest → Vitest (83%) & Rolldown (80%) But that's not all! A thread 🧵

Every test suite eventually categorizes tests: "skip this in CI," "this one is flaky," "that one needs more time." and so on. Vitest 4.1 (in beta right now) introduces Test Tags: You can now define these categories globally, attach config or behavior and eventually filter what runs.

TIL about the .extend builder pattern to add context to test fixtures in @vitest.dev Seems super handy for backend testing (setting up servers, database, mocked services etc). And now with type safety? 😍

The next @vitest.dev version has a new `test.extend` syntax that supports type inference (including the correct scope)! main.vitest.dev/guide/test-c...

Use Vitest, but don't use Vite? Vitest 4.1 introduces a new flag to disable Vite module runner entirely, but keep using all the Vitest features you like! Try it out and let us know what you think:

Test tags are coming to Vitest 4.1 (beta)! And they are powerful 💪 main.vitest.dev/guide/test-t...

The first beta for @vitest.dev 4.1 is out! 🧪 ◆ Chai-style spy assertions (`toHaveBeenCalled`, etc.) ◆ `userEvent.wheel()` for browser mode ◆ Enhanced retry options ◆ Disposable returned from `doMock()` ◆ Coverage ignore start/stop hints ◆ and more 👀 Try now by installing vitest@beta

Did you know @vitest.dev has `expect.poll`? It reruns an assertion until it passes (or times out). You can configure how many times the `expect.poll` callback should run with custom interval and timeout options! No need wrapping everything in `vi.waitFor` More in the docs vitest.dev/api/expect.h...

New Year. New Look. Same Mission. Make JavaScript developers more productive than ever before

Want to understand why some of your @vitest.dev tests are slower than expected? Then you can use the built-in experimental @opentelemetry.io support to figure out what makes tests slow and how much time is spent on each part of it. 📈

A new milestone! @vitest.dev hit 20 million mark 🎉 Took us 4 years since the first closed 0.0.0 release on December 3d, 2021 😄

What's new in ViteLand? Our November 2025 recap is out! ✨ @vite.dev 8 Beta 👉 Oxfmt alpha 💻 @vitest.dev caching and imports breakdown ⚓️ Oxc becoming even faster!? 🎙 Updates from the Community 👀 and more voidzero.dev/posts/whats-...

Vitest 4.0.15 comes with a cool experimental feature: Imports Breakdown. Every module shows how long it took to load in UI and in the VSCode extension! Pass down `--experimental.printImportBreakdown` to also see it in your terminal. vitest.dev/guide/ui.htm...

Merged! Vitest 4.0.14 includes a new tabbed view and slider for visual regression reports 🎉 This feature required a lot of work under the hood, including the creation of the new test artifacts API. Really curious to see how it'll be used by us and the ecosystem 👀

Vitest 4.0.11 adds an experimental `fsModuleCache` flag to cache module transforms between reruns. Learn more: vitest.dev/config/exper... This is an opt-in feature, please let us know how it works for you! And example of a single test file that imports a lot of files (~1500). Almost a 50% boost!

Storybook v10 is looking amazing 🤩 The new CSF, the deeper Vitest integration, so many DX wins! @storybook.js.org @vitest.dev @yannbf.bsky.social youtu.be/YNQ_cJ6yy2Q?...

What's new in ViteLand? Our October 2025 recap is out ✨ Vite+ 📣 Series A announcement 👉 @vite.dev 7.2 beta 💻 @vitest.dev 4 with stable Browser Mode ⚓️ Oxlint JS Plugins & Oxfmt pre-alpha 🎙 Updates from the Community 👀 and more voidzero.dev/posts/whats-...

Watch Jessica Sachs explain and demonstrate Vitest Browser Mode, which tests components in an actual browser instead of headless tests. Full video in comments 👇

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

Vitest vscode extension now displays your console.logs inline. An example of logging in browser mode:

What's new in ViteLand? Our August 2025 recap is out 👣 Big steps for Oxlint: Type-aware linting preview & custom JS plugins roadmap 🖼️ @vitest.dev has visual regression support in beta ⏩ Native plugins enabled by default in rolldown-vite 🤌 Smaller bundles due to @rolldown.rs and Oxc 👀 and more

Vitest 4 runs simple test files faster! You can already check it out by installing Vitest 4 beta. On average, Vitest now takes 25% less time to start the test. Due to parallelisation, the overall time difference can vary. We are focusing our efforts on improving the time even more in the next beta!

⚡ Speaker highlight: Yann Braga, Core Maintainer at @storybook.js.org Storybook is well-known as a one-stop-shop for your components and partnered with @vitest.dev to build the ultimate component testing flow. @yannbf.bsky.social will give us insights and show the full power of Storybook x Vitest

⚡ Speaker highlight: Jessica Sachs, FOSS Nerd at @hero.dev The Browser mode is one of the most exciting features of @vitest.dev! @jess.sh will reveal what makes it so powerful, moving beyond JSDOM. You’ll learn how you can use it for component testing & cases beyond A game-changer for testing! ✅

⚡ Speaker highlight: Vladimir Sheremet, Core Maintainer of @vitest.dev The State of Vitest is a must-see! @erus.dev will give us the news on the most interesting testing framework, covering the latest features, performance boosts, and what's next for the @vite.dev powered testing experience

Testing components that depend on things like localStorage or authentication can be tricky. Storybook makes it easy with our new module mocking API built on top of @vitest.dev's excellent mocking tools. storybook.js.org/blog/next-ge...

Built-in Visual Regression testing comes to Vitest in the next major release! Thank you, @macarie.blue for working on this feature 👏 main.vitest.dev/guide/browse...

Exciting early success with component testing for @react.dev server components (RSC) in @vitest.dev by @kasperpeulen.bsky.social! github.com/kasperpeulen...

Vitest Browser Mode reached almost 1.2 million weekly downloads 😮 Last time I checked it was 200k 🫣

🎉 Excited to see @analogjs.org for @angular.dev pass 50K weekly downloads and still climbing! The @vite.dev , @vitest.dev, and @nitro.build ecosystems are still growing 🚀

Highly recommend checking out @vitest.dev' Browser Mode. Not only did the setup get simpler, but to my surprise, tests got also roughly twice as fast. I only needed to rewrite one bad test suite (out of hundreds) and change the way I import MSW. Absolutely magical stuff 🪄

Wow!! @vitest.dev Browser mode is GOATED!! I moved all my test suite from playwright test to vitest browser, and things became a helluva lot simpler. Requirements: - Interactive draggability test - Cross browser testing Thread 👇

Our latest post walks through how to use the coverage reporting in Storybook 9 to be sure your components are well-tested.

Anyone knows of any good Vitest monorepo examples?

@vitest.dev is awesome. Did you know you can even mock methods that don't exist?? I called them "Ghost Methods" in this post. Reposting because my personal site was broken but I have fixed it!

Wow, love @vitest.dev is preventing me from merging PR with test.only on CI. No configuration. It just keeps me safe.

I just launched a new NPM package - a @vitest.dev utility for automated integration tests with Neon! It's really sweet. Check it out. www.npmjs.com/package/neon...

I’ve made Sveltest a thing 🫣 sveltest.dev This is documentation for getting started using vitest-browser-svelte in your projects I’m currently going through the docs sveltest.dev/docs/getting-started comparing with what me and my team are doing “real-world” and validating Contributions welcome

We've added new coverage provider comparison page on Vitest documentation. This guide describes the lower level differences between Istanbul and V8. It should help users choosing which provider to use. vitest.dev/guide/covera...

Storybook 9 is here! ▶️ Interaction tests ♿ Accessibility tests 👁️ Visual tests 🛡️ Coverage reports 🚥 Test widget 🪶 48% Leaner ✍️ Story generation 🏷️ Tag-based organization 🌐 Story globals 🏗️ Major updates for Svelte, Next.js, React Native, and more! Let’s dive in!

🤯 each @vitest.dev release is spot-on on pain points. The low latency between the pain points appearing in the community and the solution landing in Vitest is outstanding

AST based V8 code coverage is finally here! I thought of this feature first time over 2 years ago, but knew it would require so much work that I couldn't finish it by working on Vitest just on weekends. Ever since @stackblitz.com hired me to work on Vitest I knew I could finish features like this.

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

The next talk from Svelte Summit Spring 2025 by @reinhold.is is also related to testing — Strike the Perfect Balance: Component Testing with Storybook, Svelte, and Vitest. youtu.be/mdyRQDDp28s

🔥 The latest release of @analogjs.org for @angular.dev is out! ✅ Angular v20 support ⚡Stable @vitest.dev support across multiple versions of Angular 🤖 Improved support for generating new Analog apps with @nx.dev github.com/analogjs/ana...

In today's released talk from Svelte Summit Spring 2025 @dominikg.dev talks extensively about testing your Svelte applications with Vitest and Playwright — Testing, 1 2 3 4. www.youtube.com/watch?v=ljmU...

After watching, make sure to check out @scottspence.dev blog post about this. bsky.app/profile/scot... He not only applied the patterns i showed in my talk but also expanded and improved on them, with feedback from @erus.dev too. A great testament of collaboration in our communities.