Michael Dong

Vitest Next generation testing framework powered by Vite

Browser mode just became stable in the latest major (v4)!

vitest.dev/guide/browser/

@hiogawa.bsky.social - Good job!

Good stuff!

It's a transition step between Vite 7 > Vite 8 for the underlying bundler. Vite 8 will replace esbuild & rollup with rolldown, which is
1/ written rust & faster
2/ consistent between dev & prod

Rolldown-vite was a way to test this migration make it more stable before the Vite 8 release

Big up to new #oxc contributor @arsh.sh, who showed up out of nowhere and is tearing through our issue list! He's just implemented support for all the comment-based APIs in Oxlint JS plugins. github.com/oxc-project/...

DAAANGGGGG. The pasta looks delicious

This is, to an extent, already happening. But in parts. Vite & Vitest have become best-in-class tools. Our goal is to make oxlint & oxfmt the same.

Vite+ will make it easier. Install once. Get best tools. Focus on more important work.

Vite is switching to Rolldown for both dev & prod in next version, Vite 8. Should solve that concern

Formatter coming soon. Already at >92% prettier test conformance

Glad you're excited. Our goal has always been to build best-in-class tools and improve DX

And the community that formed around it!

This looks awesome

Adoption’s also why we’ll continue to improve features in OSS like Vite. The more people that adopt Vite, the more people will adopt Vite+

fix(rolldown): sync scoping properly in pre_process_ecma_ast by Boshen · Pull Request #6537 · rolldown/rolldown We need to recreate scoping after each transformation step because none of the steps syncs scoping at present, which is a huge waste that we should fix later in the future. But in the interim, defi...

In the next version of Rolldown, bundling will be ~10% faster 🎉

This was achieved by optimizing the semantic scoping process

Internal plugins like define and inject now flag when they haven't changed the AST, allowing to skip redundant scope recreation

github.com/rolldown/rol...

The daily watch :D

Watch @antfu.me talk about the new @vite.dev Devtools and what Vite DevTools Plugin means.

Full video in comment 👇

Watch VoidZero’s @overlookmotel.bsky.social explain how oxlint tackles JS-Rust interoperability to maintain high performance for plugins.

Full video in comment 👇

If you're using vite+ but don't want to use oxlint, then we're doing something wrong...

Fair point. End of the day is the juice worth the squeeze?

Vite+'s value prop is that the dev time saved from configs, dependency management, security review, etc is worth more than the price.

Since that time can be used on features & generating biz value instead

Announcing Vite+ Introducing Vite+, a unified toolchain for JavaScript.

More details: voidzero.dev/posts/announ...

Not super novel. For most companies, revenue isnt uniformly distributed and instead follow the pareto rule, where the majority of revenue comes from the top accounts.

Meaning top accounts subsidize dev, maintenance, etc for free or lower paying users to enjoy. Vite+ is the same for OSS

Take care. You'll be missed ♥️

Looking forward to hearing your talk!

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

Rolldown will be the default Vite bundler soon!

How PLAID Cut Build Times by 97% Migrating From Rollup To Rolldown The PLAID developer experience team migrated from Rollup to Rolldown for their server-side bundling, seeing a 97% build times decreased

PLAID Moved to @rolldown.rs & Cut Build Times by 97%

PLAID was using Rollup for server-side bundling, which could take up to 20s to complete each time! The team wanted to reduce wait times.

Learn why the PLAID team migrated to Rolldown.

voidzero.dev/posts/case-s...

Done! Thanks for catching

Thanks for sharing!

ViteConf 2025 speaker card of Jessica Sachs, who is an FOSS Enthusiast and working at HeroDevs. Her talk will be all around the Vitest Browser Mode

⚡ 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! ✅

The example of a test that tests an element is consistent between code changes. The code includes `expect(element).toMatchScreenshot('hero-secion')`

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