VoidZero — the team responsible for Vite, Vitest, Rolldown, Oxc, and Vite+ — is now part of Cloudflare. As part of this transition, every member of the VoidZero team is joining Cloudflare as well.
Before going any further, let’s state the most critical point upfront: Vite, Vitest, Rolldown, Oxc, and Vite+ will remain open source, independent of any single vendor, and guided by their communities. None of that is changing.
Cloudflare’s mission is to help create a better Internet. And a better Internet is an open one. Developers deserve choice, frameworks need a neutral home, and applications should be free to run anywhere. It’s unrealistic to expect the entire web ecosystem to revolve around one company. The most impactful tools and frameworks are built to be portable from the start.
Vite is one of the rare foundational tools that the entire JavaScript community has rallied around. It earned that status through speed, quality, portability, and vendor neutrality. One of the most meaningful ways Cloudflare can contribute to a better Internet is by investing in that foundational open source toolchain — a toolchain that benefits everyone, not just those who use Cloudflare or host with us.
Over the past several years, we’ve poured significant effort into making Cloudflare the ideal place to build and deploy websites, applications, and agents on our developer platform
. But the choice will always be yours. Deploy your Vite application wherever you prefer.
Today’s announcement brings Vite additional resources to keep expanding, while everything that defines Vite stays unchanged:
Vite stays MIT-licensed and open source.
Vite stays vendor-neutral. Apps built with Vite run anywhere, and that won’t change.
Vite’s roadmap continues to be shaped by the broader Vite team and community, with development happening in the open.
Evan and the rest of the VoidZero team remain at the helm of Vite, Vitest, Rolldown, Oxc, and Vite+.
Cloudflare is dedicating engineering talent and resources to these projects, not pulling them in a different direction.
We made a similar pledge when Astro joined Cloudflare earlier this year. Astro is still open source and still deploys anywhere. The team continues to deliver on the roadmap they already had in motion.
This commitment carries even greater weight with Vite, because Vite isn’t just one framework. Vite is the shared foundation beneath so many: Vue, SvelteKit, Nuxt, Astro, Solid, Qwik, Angular, React Router, TanStack Start. Even Next.js now has a Vite-powered implementation in vinext. Vite has become a common pillar for the JavaScript ecosystem.
Our top priority is preserving the trust that drove Vite’s widespread adoption. Not through statements here, but by demonstrating it every day in how we support and evolve these projects.
We also want to back up our words with real investment in open source and shared ecosystem foundations. As part of this announcement, Cloudflare is pledging $1 million to a Vite ecosystem fund to support maintainers and contributors, overseen by the Vite core team. Vite is bigger than VoidZero or Cloudflare, and the people who helped build it should share in what comes next.
The Vite and Cloudflare teams have been working together well before this announcement, going back to 2024 with the Vite Environment API. The Environment API allows Vite to execute server code in environments beyond Node.js during development. We collaborated closely with the Vite team on its design, then built the Cloudflare Vite plugin on top of it.
When you run vite dev with the Cloudflare plugin, your server code runs inside workerd — the same open-source runtime that powers Workers in production. Durable Objects, D1, KV, R2, Workflows, Workers AI, Agents, Service Bindings, Workers RPC — everything runs locally using the same runtime model as production.
For a long time, the trade-off of developing on a non-Node runtime was that local development felt like a downgraded version of production. The Environment API eliminated that trade-off without requiring anyone to adopt a Cloudflare-specific dev server. Any runtime that wants to integrate with Vite can do the same. That pattern — a generic mechanism in Vite with provider-specific implementations — has proven effective and is something we want to keep building on.
We knew we were onto something significant when adoption of the Cloudflare Vite plugin surged:
Vite’s growth trajectory is one of the most impressive things happening in the ecosystem right now. As of this writing, Vite sits at roughly 129M weekly downloads. The Cloudflare Vite plugin (@cloudflare/vite-plugin) is nearing 14M weekly downloads.
If you’d told us a year ago that a Cloudflare Vite plugin would reach download numbers equivalent to more than 10% of Vite itself, we wouldn’t have believed it. What changed? AI. More software is being created than ever before, and much of it begins with AI-generated code. Those applications need a default stack and a place to run. Agent-built applications are choosing Vite, and increasingly they’re choosing Vite running on Cloudflare.
AI is transforming how we write software
Developers used to be the sole users of dev servers, bundlers, linters, formatters, and CLIs. That’s no longer the case: AI agents are using them too, constantly. They scaffold projects, launch dev servers, read errors, write tests, lint and format code, deploy previews, and iterate.
A large share of AI-generated applications already begin as Vite apps, because Vite is fast, well-documented, and widely compatible with what agents have encountered in their training data. Fast feedback loops have always been essential. They become even more crucial when building software with agents:
Fast builds, because agents iterate far more than humans do.
Fast tests, because they re-run the suite repeatedly to verify their own output.
Fast linting and formatting, because those tools serve as guardrails.
Clear, well-structured errors, because the agent needs to interpret and act on them.
Consistent CLIs, because even small inconsistencies lead to major detours.
The entire VoidZero toolchain is purpose-built for this kind of loop. Vitest, Rolldown, Oxc, Oxlint, and Oxfmt are each among the fastest tools in their respective categories, and they perform well when executed repeatedly by an agent. Vite+ unifies those pieces into a single toolchain — one CLI, one configuration model, fewer moving parts. That makes the development loop simpler for people to grasp and easier for agents to operate reliably.
We’re using this ourselves. The Cloudflare dashboard is built on Vite. Oxlint is already saving days of engineering time across Cloudflare codebases.
Flue, the agent harness framework from the Astro team, is also transitioning to Vite as its core. Flue supports running agents on Node.js, Cloudflare Workers, GitHub Actions, GitLab CI/CD, and other environments, with the Cloudflare target now leveraging the official Cloudflare Vite plugin and workerd integration. Vite is also becoming the standard application foundation within Cloudflare itself.
Vite is evolving into a full-stack solution
A few years back, build tools had a simple role: process source files, generate a bundle, and deliver it. That approach no longer suffices for today’s applications, particularly as some of those applications are now agents themselves.
Today’s applications encompass server-rendered routes, APIs, background tasks, queues, databases, object storage, real-time features, authentication, along with an expanding array of agents and AI capabilities. The “build” is no longer the final step. It marks the beginning of a deployment process that must account for all these components.
This evolution demands that Vite grow beyond being just a build tool. It needs to comprehend more aspects of the application, while preserving the qualities that made Vite successful: speed, simplicity, and portability.
Void, a deployment platform built specifically for Vite, has served as another testing ground for these concepts. It helped define what a modern application framework should manage, what deployment should feel like, and how much of the complete application lifecycle can be consolidated within a single toolchain. We have gained valuable insights from that experience.
Now the focus is on applying those lessons where they fit best. Some belong in Vite itself as provider-agnostic building blocks: first-class abstractions and hooks for backends, APIs, agents, and deployment that any provider can adopt. Other lessons are being integrated into Cloudflare. Cloudflare will deliver a first-class implementation of those hooks on Workers and across our Developer Platform.
Even as some Vite maintainers join Cloudflare, changes to Vite will continue to follow the same open contribution process as any other Vite contribution. Features introduced to Vite itself will not be Cloudflare-specific. They will function wherever Vite runs.
Aligning Cloudflare with Vite
The same principle guided our thinking about the future of Cloudflare’s own tooling. We are not reshaping Vite to fit Cloudflare. We are doing the reverse: migrating Cloudflare’s application tooling onto Vite, so it builds upon the workflows developers already use.
We recently released a technical preview of cf, a new unified CLI for the entire Cloudflare platform. Vite will serve as the foundation for our CLI experience with applications. The ultimate goal is a single, consistent CLI for all of Cloudflare, with the same developer experience whether you are working with Workers, R2, D1, Agents, or any other service.
If we execute this well, the Cloudflare CLI should feel like a natural extension of Vite, not a separate tool awkwardly attached alongside it.
cf devshould extendvite devas a superset. Same speed, same hot module replacement, same plugin architecture, with the added Cloudflare runtime and bindings available when you need them.cf buildshould natively understand Vite projects, without requiring adapter workarounds.cf deployshould make deploying a Vite app to Cloudflare straightforward.
If you are already using Vite today, moving to Cloudflare will feel like adopting a superset of the commands you already know. Same project structure. Same Vite workflows. The full Cloudflare developer platform accessible whenever you need it.
In the near term, nothing changes for Vite users or the frameworks built on top of Vite:
Vite, Vitest, Rolldown, Oxc, and Vite+ continue to ship updates. The VoidZero team continues to contribute to and lead these projects.
The Cloudflare Vite plugin continues to improve.
The Environment API and the broader effort to “run your server code in the right runtime locally” continues to advance, including support for non-Cloudflare runtimes.
Looking further ahead:
We begin work on evolving the Cloudflare CLI toward an experience built natively on top of Vite.
Vite will receive new, well-designed, provider-agnostic primitives for full-stack applications and agents that work for everyone on any platform.
Over time, we plan to open-source the Void platform, enabling others to learn from it and build their own platforms on top of Vite and Cloudflare.
We will carry out all of this publicly and alongside the community. The same way Vite has always been developed.
Vite, Vitest, Rolldown, Oxc, and Vite+ exist because a vibrant ecosystem of open source contributors dedicated years of effort to them. These projects are already fundamental to how the web is built, and we are thankful to everyone who helped bring them to this point. Thank you to everyone who has contributed code, reviews, issues, documentation, plugins, integrations, and support along the way.
We are thrilled to welcome the VoidZero team to Cloudflare, and eager to invest more resources into these projects. Our responsibility now is to help them grow, remain open, and power the JavaScript ecosystem for everyone.
Vite continues to be Vite. Cloudflare gets to contribute.
If you want to try Vite on Cloudflare today, run:
npm create vite@latest
npx wrangler deploy
