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.

Cloudflare supports Vite's mission

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

vite.dev

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.

Rolldown v1.0.0-rc.16 is out 🎉 - Support cross-module const enum inlining - Fix empty module namespace in `manualChunks` - Fix wildcard re-exports with transitive top-level await - More bug fixes and improvements github.com/rolldown/rol...

Release v1.0.0-rc.16 · rolldown/rolldown

[1.0.0-rc.16] - 2026-04-16 🚀 Features const enum cross-module inlining support (#8796) by @Dunqing implement module tagging system for code splitting (#9045) by @hyf0 🐛 Bug Fixes rolldown_plugin...

github.com

SvelteKit 2 now fully supports Vite 8 SvelteKit 3 will require it - giving additional optimizations and functionality. E.g. SvelteKit 3 will use @rolldown.rs hook filters to spend more compilation time in rust and less in JavaScript. And SvelteKit 3 adapters use only rolldown without esbuild

Rolldown can panic sometimes... but we make sure you never have to! It's rare, but when it happens, you won't be staring at a cryptic stack trace. @rolldown.rs straight up tells you it is not your code. And a link to report it so we can fix it fast. Good error messages => good DX

✨ 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 🧵

🚀 Lazy Barrel Optimization in Rolldown Barrel files, files that re-export from other modules, are common in modern JavaScript projects but a nightmare for your build time. Rolldown now has Lazy Barrel Optimization to fix this. Here's how it works 🧵

🔍 @rolldown.rs can now automatically discover your tsconfig, similar to how @vite.dev does it, respecting `references`. The feature was available beforehand but is now enabled by default! Don't want auto discovery? Then provide a path to another config More in the docs rolldown.rs/reference/In...

Rolldown | Rust bundler for JavaScript

Fast Rust-based bundler for JavaScript with Rollup-compatible API

rolldown.rs

✨

VoidZero@voidzero.dev · 7mo ago

Rolldown 1.0 RC is here 🎉 🔒 Stable API: No breaking changes planned before 1.0 ⚡ 10-30x faster than Rollup while staying compatible 🧩 Multiple chunking algorithm improvements 📦 3,400+ commits since beta: 749 features, 682 fixes, 109 perf optimizations

In the next version of Rolldown, you can automatically clean up the previous build when rebuilding by setting `output.cleanDir` to true 🧹 Thanks to @aprosail for the contribution! github.com/rolldown/rol...

Watch VoidZero's @thealexlichter.com spill the tea about @rolldown.rs and bundlers. Why bundlers are needed and how come @vite.dev is migrating to Rolldown in Vite 8. Full video in comment 👇

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

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

github.com

Building performant tools doesn't happen by accident. They need a strong foundation! @rolldown.rs and @vite.dev 8 are powered by Oxc for that reason We've evaluated all previous PRs that went into the Oxidation compiler, 290 of them improving performance This is what foundational work looks like!

Said no one ever 👀

Alexander Lichter@thealexlichter.com · 10mo ago

State of JS 2025 Christmas is only 3 months away, which means it is also time to take the State of JavaScript survey (again). The more devs participate, the clearer the big picture will be in the end 🙌 Plus, you learn about features, libs, and frameworks you haven't heard before (or forgot about).

Another beta - another bunch of improvements 🔥 Also includes changes from the latest Oxc version!

VoidZero@voidzero.dev · 11mo ago

Rolldown v1.0.0-beta.39 has been released! ⚡ macOS Performance Boost: 10%-30% faster bundling, up to 45% in extreme cases. 🎯 Cross-Chunk Optimization: Support for __NO_SIDE_EFFECTS__ annotation, as well as better tree-shaking across module boundaries and more efficient DCE

Faster on Windows ✔

sapphi_red@sapphi.red · 11mo ago

Windows users, I have a good news for you. In the next version, Rolldown will become ~10% faster on Windows — even up to 29% faster in some cases! 🚀

Rolldown drops CJS support! From the latest version of @rolldown.rs (1.0.0-beta.36) on, Rolldown will only be released in the ESM format. The required Node version has also been bumped to align with @vite.dev (20.19+ and 22.12+). Node 18 has been dropped due to being EOL since April.

tsup is not actively maintained anymore 👀 With >9M NPM monthly downloads and >10k GitHub stars, tsup is undeniably a popular choice for bundling. Unfortunately, it is not under active maintenance anymore. Thanks to @egoist.dev & contributors for all the work on tsup 🙏🏻

In the latest @rolldown.rs powered @vite.dev version, we've enabled the rust-based resolver plugin by default! This will lead to even faster builds in case you don't use the experimental native plugins yet. Wanna try out more native core plugins? Then enable them and make sure to use rolldown-vite

Rolldown Integration

Next Generation Frontend Tooling

vite.dev

`oxlint --type-aware`. Mic drop. It's incomplete and have numerous problems, including a noticeable performance issue. BUT, you can finally see your floating promises quickly! Example PR: github.com/rolldown/rol... Problems: t.co/K7ZVnPjOPL

Remember how @gitlab.com got 2.6x faster builds and ~100x less memory consumption when using @rolldown.rs? Now, with all the native plugins enabled, they are down to 22s. That is ~7x faster than Vite, ~half the time compared to using native resolver before and 43x faster than their webpack build 🔥

Alexander Lichter@thealexlichter.com · last yr.

ICYMI: GitLab saw their memory consumption reduced by 100x by using the @rolldown.rs powered @vite.dev version (in addition to a 2.6x speedup) 🤯

What's new in ViteLand? Our July 2025 recap is out. 🎉 Announcing 1st in-person @viteconf.org in Amsterdam 📈 @vite.dev surpassing webpack's downloads ⏩ Major performance boosts for @rolldown.rs 🔥 Type-aware linting & custom rules for Oxlint 👀 and more Read the post: voidzero.dev/posts/whats-...

What’s New in ViteLand: July 2025 Recap

July 2025 brings exciting updates in the Vite ecosystem, including the release of Vite 7, Rolldown's new features, and the upcoming ViteConf in Amsterdam. Discover the latest news in Vite, Vitest, Oxc...

voidzero.dev

Did you know that @rolldown.rs supports converting your top-level variables to var? It seems weird at first, but is actually helpful - and your output is still ESM and modern code! The transform can improve perf due to avoiding "temporal dead zone" checks of VMs that can cause slowdowns up to 1000%

👀👀👀

ViteConf@viteconf.org · last yr.

⚡ Speaker highlight: Evan You ViteConf wouldn’t be the same without @evanyou.me, creator of Vue & Vite. His talks always drop major news 👀 This year, he'll reveal how Vite is evolving beyond a build tool into a full Rust-based toolchain. You won't want to miss it! More info on viteconf.amsterdam

Wow! @sapphi.red just made @rolldown.rs Vite's startup time 2x quicker. How? By dealing with PIFEs and optimizing for the v8 engine, also coming to Oxc 👀 Everyone knows IIFEs but PIFEs? 😁 Really impressed by such deep knowledge 👏

✨ Node.js: Now with Rolldown? Yes - to some degree! @rolldown.rs is planned to power the future API documentation generator of @nodejs.org. More info in the linked PR! github.com/nodejs/api-d...

feat(web): add web generator by avivkeller · Pull Request #285 · nodejs/api-docs-tooling

Fixes #7. This PR adds the web generator. Tasks / Issues P1 – Must Complete Before Merge Add more items (anyone can do this as they review1) P2 – Must complete before migration Add more items ...

github.com

🚨 Speaker Alert 🚨 We're incredibly proud to bring together an exceptional group of speakers who are pushing the boundaries of web development with @vite.dev Over the next few days, we'll be highlighting the incredible speakers who will be on our stage on Oct 9-10! Stay tuned 🚀 viteconf.amsterdam

Did you know that Rolldown-Vite supports tsconfig path resolution out of the box? Use the path resolutions defined in your tsconfig by setting `resolve.tsconfigPaths`. The only requirement? You must use native plugins, either only the resolver or all No extra plugin needed 🙌