iiinova — where your digital self keeps evolving

Reposted by Vitest

VoidZero @voidzero.dev · 28/09/2026

Vite+ 1.0 is here 🚀 A single `vp` CLI for managing your Node.js runtime, package manager, and frontend toolchain. Built on top of Vite, Vitest, Rolldown, Oxc, and tsdown. All with a single config. Free and open source under the MIT license. Start with `vp create` or migrate with `vp migrate`.

voidzero.dev

Announcing Vite+ 1.0

Vite+ 1.0 is here. One CLI manages your runtime, package manager, and frontend toolchain.

213532

Reposted by Vitest

AriPerkkio @ariperkkio.dev · 28/09/2026

This Thursday we'll be discussing about Visual Regression Testing using @vitest.dev and @chromatic.com. Join me and @kylegach.com to hear how you can get VRT that's stable across your whole team, not just on your local machine. 📸

0139

Reposted by Vitest

Chromatic @chromatic.com · 24/09/2026

@vitest.dev already renders your components in a real browser. Now you can visually test them there, with no test code changes. 🎙️ @ariperkkio.dev, the Vitest core maintainer who built our new plugin, is doing a live walkthru with @kylegach.com to show you how. 🎟️ Save your spot 👇

How to visually test your components with Vitest & Chromatic

1151

Vitest @vitest.dev · 17/09/2026

🚀 Vitest 5.0.1 is out with more than 18 fixes Among them: `define` values are no longer double-quoted in browser mode! It also includes a focused Trace View layout which is used by the Vitest VS Code extension. Time to update 👀 github.com/vitest-dev/v...

github.com

Release v5.0.1 · vitest-dev/vitest

🚀 Features ui: Move trace attempts selector to viewer header - by @hi-ogawa, Hiroshi Ogawa and Codex in #11189 (5dc4b) Add focused trace view layout mode - by @hi-ogawa, Hiroshi Ogawa, Ope...

0428

Reposted by Vitest

James @43081j.com · 09/09/2026

Big win! Migrated the whole @netlify.com build repo to @vitest.dev 🎉🎉 Also made heavy use of my snapshot diff tool since ava has binary snapshots (accounting for most of the 40k+ PR 😅)

2365

Reposted by Vitest

Alexander Karan @alexanderkaran.bsky.social · 05/09/2026

I’m gonna be honest my life is so much happier with Vitest in it.

1413

Reposted by Vitest

Chromatic @chromatic.com · 03/09/2026

Chromatic for @vitest.dev Browser Mode is live. 🧪📸 Browser Mode runs your component tests in a real browser. Now Chromatic checks how those components look by capturing the rendered UI. No new screenshot assertions. No second suite to maintain. 🧵 (1/4)

Vitest Visual Regression Testing with Chromatic

1244

Vitest @vitest.dev · 03/09/2026

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!

vitest.dev

Announcing Vitest 5.0

Vitest 5.0 Release Announcement

221744

Reposted by Vitest

Matija Marohnić @silvenon.com · 31/08/2026

The @vitest.dev v5 rc is very exciting, performance is great, and all of my wishes are fulfilled ❤️ Trace view is such a killer feature, I'm so happy I didn't have to wait for the stable release to use it.

0224

Reposted by Vitest

AriPerkkio @ariperkkio.dev · 27/08/2026

The @vitest/istanbuljs fork is now ready and will ship in the next version of Vitest. Compared to the original istanbuljs packages it's ESM-only, ships its own typings, drops unnecessary runtime deps, and moves Node 8→22, Babel 7→8 (lib-instrument), React→Preact (html-spa reporter), and more!

github.com

Release v1.0.0 · vitest-dev/istanbuljs

v1.0.0 First stable release of @vitest/istanbuljs, a fork of istanbuljs/istanbuljs maintained by the Vitest team. The fork starts at upstream commit 28ffdbc (see vitest-dev/vitest#9433 for backgrou...

24411

Reposted by Vitest

James @43081j.com · 18/08/2026

bit of a niche thing but i put a tool together for diffing ava and vitest snapshots. migrating from ava to vitest is a pain because: - vitest snapshots are text - ava snapshots are encoded values, cbor'd, then gzipped this tool lets you confirm your new vitest snapshots match the old ones

github.com

GitHub - 43081j/ava-vitest-snapshot-diff: A tool to diff ava and vitest snapshots.

A tool to diff ava and vitest snapshots. Contribute to 43081j/ava-vitest-snapshot-diff development by creating an account on GitHub.

0172

Reposted by Vitest

AriPerkkio @ariperkkio.dev · 05/08/2026

TIL when running Vitest browser mode (or plain Playwright) on Github Actions on Ubuntu, you can skip the slow "playwright install chromium" step completely by providing channel option. This makes Playwright use the pre-installed Chrome. So many projects out there that could speed their CIs with this

Github PR diff view showing removal of "playwright install" step, and addition of "launchOptions.channel: 'chrome'" on Vitest Playwright provider.

41149

Reposted by Vitest

Vladimir @vladimir.berlin · 24/07/2026

@vitest.dev 5-beta.7 is out with a lot of performance improvements depending on your setup. If you are using jsdom, consider switching to vmThreads pool for x4 speedup! Are your tests now running faster? github.com/vitest-dev/v...

A table with performance data for different types of app:

deps-heavy, vm pools (warm + cold) −53…−58%
micro-utils, vm pools warm −22…−29%
enterprise-monolith, forks isolate:true −21…−33%
node-library, all cells −9…−27%
node-backend, vm pools −22…−28%
browser mode (react-spa/vue-spa/design-system) −7…−18%
jsdom warm rows across SPA apps −8…−22%

1397

Reposted by Vitest

Vladimir @vladimir.berlin · 10/07/2026

`vmThreads` is 30% faster in Vitest 5 for your jsdom tests. It is now a much better alternative to the default forks+jsdom. Vitest 5 also comes with a `vitest doctor` command that will find the best settings for you! As a note, browser mode also becomes ~30% faster, but for different reasons :)

an app with 342 modules + real deps is ~32% faster. 1022 modules + heavier deps is ~28% faster

0579

Reposted by Vitest

Marvin Hagemeister @marvinh.dev · 02/07/2026

How to speed up vitest: De-barrel everything so that the module graph gets smaller. Saves both processing + import time. And get rid of module mocks, which prevents many de-barelling opportunities.

4606

Reposted by Vitest

Vladimir @vladimir.berlin · 18/06/2026

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

github.com

Sponsor @vitest-dev on GitHub Sponsors

1244

Reposted by Vitest

Kate Holterhoff, PhD @kateholterhoff.com · 16/06/2026

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...

youtube.com

Cloudflare's VoidZero #acquisition & #oss commitments with Evan You #startup

YouTube video by RedMonk

0235

Reposted by Vitest

Chromatic @chromatic.com · 11/06/2026

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 🧵

Early access. Vitest Browser Mode visual tests in Chromatic for free (while in beta for the summer)

1163

Reposted by Vitest

VoidZero @voidzero.dev · 10/06/2026

🌌 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.dev

Tales from the Void: May 2026 Recap

Our May 2026 recap covers VoidZero joining Cloudflare, Rolldown reaching 1.0 stable, and more.

1453

Reposted by Vitest

VoidZero @voidzero.dev · 04/06/2026

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.

1027756

Reposted by Vitest

Vite @vite.dev · 04/06/2026

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.

vite.dev

Cloudflare supports Vite's mission

The VoidZero team is joining Cloudflare. Vite remains MIT, vendor-neutral and stewarded by the same wider team.

521238

Vitest @vitest.dev · 01/06/2026

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...

github.com

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`,...

0266

Reposted by Vitest

AriPerkkio @ariperkkio.dev · 01/06/2026

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.

1237

Reposted by Vitest

Chromatic @chromatic.com · 28/05/2026

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)

vitest-chromatic-integration-early-access-program

3538

Reposted by Vitest

Younes Jaaidi @younesjd.dev · 22/05/2026

🦸 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.

Screenshot of a video call with six participants in a grid layout. Three participants have cameras on in the top row: a smiling woman with glasses and a space-themed virtual background, a man in an apron smiling in front of copper pans and kitchen decor, and a woman waving in a bright room. In the bottom row, a man wearing headphones waves at the camera with a blurred background, another woman waves while smiling, and one participant has their camera off with the name ‘Hugo’ displayed on a black screen.

191

Vitest @vitest.dev · 19/05/2026

🚨 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

github.com

Build software better, together

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

04210

Reposted by Vitest

VoidZero @voidzero.dev · 16/05/2026

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

05110

Reposted by Vitest

Younes Jaaidi @younesjd.dev · 07/05/2026

🫡 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...

github.com

feat(@schematics/angular): add option to migrate `fakeAsync` to Vitest fake timers by yjaaidi · Pull Request #33111 · angular/angular-cli

PR Checklist Please check to confirm your PR fulfills the following requirements: The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-com...

1193

Reposted by Vitest

VoidZero @voidzero.dev · 06/05/2026

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

voidzero.dev

Tales from the Void: April 2026 Recap

Our April 2026 recap covers VoidZero's approach to supply chain security and trusted publishing, an Oxc-based Angular Compiler 6.4x faster than the Angular CLI, Vite+ lazyPlugin, a new Vitest trace…

1485

Reposted by Vitest

Vladimir @vladimir.berlin · 27/04/2026

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...

The new trace viewer. It shows the state of the DOM at certain points and also shows when the state was changed in your code.

59511

Reposted by Vitest

Vladimir @vladimir.berlin · 20/04/2026

what are these downloads numbers 🤨

A graph showing a difference in downloads of vitest (50.6M) vs jest (42.8M)

5545

Reposted by Vitest

VoidZero @voidzero.dev · 16/04/2026

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.

A screenshot of the docs showcasing the agent reporter feature

27112

Reposted by Vitest

AriPerkkio @ariperkkio.dev · 15/04/2026

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.

github.com

GitHub - fallow-rs/oxc-coverage-instrument: Istanbul-compatible JavaScript/TypeScript coverage instrumentation using the Oxc AST

Istanbul-compatible JavaScript/TypeScript coverage instrumentation using the Oxc AST - fallow-rs/oxc-coverage-instrument

1257

Reposted by Vitest

Jens Rømer @jensroemer.com · 13/04/2026

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 👏

0193

Reposted by Vitest

James @43081j.com · 12/04/2026

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

1421

Reposted by Vitest

Alexander Lichter @thealexlichter.com · 09/04/2026

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 🎉

Navbar of Vitest's "learn" section in the docs, showing menu items like "Using Matchers" or "Writing Tests with AI"

36012

Reposted by Vitest

Vladimir @vladimir.berlin · 07/04/2026

@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...

Running tests with `--experimental.preParse` runs only a single test file unlike previously when it would only apply `.only` per test file

1478

Reposted by Vitest

VoidZero @voidzero.dev · 31/03/2026

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?

4384

Reposted by Vitest

fast-check @fast-check.dev · 27/03/2026

🖇️ 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...

npmx.dev

@fast-check/vitest - npmx

Property based testing for Vitest based on fast-check

2153

Reposted by Vitest

Ilja @fubits.dev · 24/03/2026

👁️ 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...

npmx.dev

npmx

291

Reposted by Vitest

Vite @vite.dev · 18/03/2026

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 💜

vite.dev

5th anniversary of the Vite Team Creation

Vite: The Documentary re-premiere. Join the ecosystem this March 19th at 3 PM UTC to remember the story we wrote together. And participate in the live stage to discuss our past, present, and future. W...

2417

Reposted by Vitest

AriPerkkio @ariperkkio.dev · 18/03/2026

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.

github.com

test(reporters): add outputFile tests by AriPerkkio · Pull Request #978 · vitest-dev/vitest

Adds missing test cases for outputFile configuration. I'm working on another bug fix and thought let's merge these ones first.

2368

Reposted by Vitest

Younes Jaaidi @younesjd.dev · 17/03/2026

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...

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.

3375