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?
Posts by Vitest
👏 @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 graph of Vitest downloads on npmx.dev: 42.8M as of now. The graph starts slow, but jumps after the new year showing +20M more downloads in 3 months.
🫣
👁️ 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.
Slide comparing manual vs automatic handling of fake timers in a Vitest test. Top-left code shows a test using fake timers manually: • vi.runAllTimersAsync() to flush framework internals (e.g. Angular sync) • vi.advanceTimersByTimeAsync(300) to handle debounce Annotations explain both steps are required and can slow tests. Bottom-left note explains that since Vitest 4.1.0, a “fast-forward” mode can automatically advance timers. Right side shows simplified code using: • vi.setTimerTickMode('nextTimerAsync') No manual timer flushing or advancing is needed. Footer includes author handle (@yjaaidi / @younesjd.dev) and a link to marmicode testing content.
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...
Slack DM from November 15th, 2024. Younes Jaaidi: "My speculation is that Vitest will surpass Jest usage by Q1 2026 🔮". Brandon Roberts replies: "2026! 💀"
npmx.dev chart showing Jest vs Vitest monthly downloads from Nov 2024 to Mar 2026. Vitest grows from ~30M to 155.5M, surpassing Jest which sits at 143.3M. The lines cross around Q1 2026.
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!
A screenshot of a PR with the title "feat: support deno runtime"
@vitest.dev vscode extension now supports @deno.land!
A screenshot of macOS terminal showing a test suite summary for Elena.
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!
GitHub pull request page showing ‘refactor: remove experimental Jest and Web Test Runner builders #32582’ merged into angular:main. The screenshot highlights the pull request summary with 29 files changed, 34 checks, and a large red ‘−2,938’ code deletion indicator pointed to by a purple arrow.
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...
Vitest console output showing 993 tests passed across 3 files
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!
Terminal output of Vitest's test run results. The results contain error message of asynchronous resource leaking. Code block pointing to a fetch call that is missing await.
In the next version of Vitest you can track leaking asynchronous resources via `--detect-async-leaks` option! Available in v4.1.0-beta.4 release. 🔍
(notice missing await in the example)
👋 @vitest.dev Browser Mode for #Angular is not just a switch — but a different recipe 😉
Let's dive into what's cooking under the hood:
⚙️ How it works (Vitest vs Playwright roles)
🌓 "Partial" vs. 🌕 "Full" Browser Mode
🔌 APIs: userEvent vs. page
🪜 Progressive migration
youtu.be/Pu22JQG6jdg
#testing
What stops you from using @vitest.dev browser mode? 👀