VoidZero is joining Cloudflare

VoidZero, the company behind Vitae, wittest, rolling out, oxcAnd vitae+Joining Cloudflare. As part of this transition, all VoidZero team members are also joining Cloudflare.

Before we say anything else, we want to make the most important thing clear: Wight, Wightest, Rolldown, Oxy, and Wight+ will remain open source, vendor-agnostic, and community-driven. Nothing changes about that.

Cloudflare’s mission is to help build a better Internet. And a better Internet is an open Internet. Developers need options, frameworks need a neutral base, and applications need to be portable. It is not reasonable to expect the entire web ecosystem to be built around a single vendor. The most important tools and structures are portable by design.

Vite is one of the few fundamental tools that the entire JavaScript ecosystem agrees on. It earned this spot because it was fast, excellent, portable, and vendor-neutral. One of the best ways Cloudflare can help build a better Internet is to invest in that foundational open source toolchain. A toolchain that makes the Internet better for everyone, not just those who use Cloudflare or choose to host with us.

Over the past few years we’ve invested heavily in making Cloudflare the best place to build and run websites, applications, and agents. developer forum. But ultimately that choice will always be yours. Run your Vite application anywhere you want.

Today’s news gives Vitae even more resources to move forward, while the things that make Vitae what it is remain the same:

• Vite remains MIT-licensed and open source.

• Witte remains vendor-agnostic. Applications built with Vite can and will run anywhere.

• Vite’s roadmap is being driven by the broader Vite team and community, and is being developed openly.

• Evan and the rest of the VoidZero team continue to lead Vite, Vitest, Rolldown, Oxc and Vite+.

• Cloudflare is dedicating engineering and resources to those projects, not redirecting them.

We had also made a similar commitment then Astro joins Cloudflare earlier this year. Astro is still open source, and still deployed somewhere. The team is still sending the same roadmap they were already sending.

With Vitae this commitment is even more important, because Vitae is not a single framework. Vitae is the underlying foundation of many: vue, Sweltekit, next, Astronomy, Solid, quick, angular, react router, tanstack start. even next.js It now has a wight-based implementation Vinext. White has become a shared substrate for the JavaScript ecosystem.

Our number one goal is to maintain the trust that has made Vitae so popular. Not with our words here, but by proving it every day in how we support and grow these projects.

We also want to put our money where our mouth is when it comes to our support for open source and shared ecosystem foundations. As part of this announcement, Cloudflare is pledging $1 million to the Whitespace Ecosystem Fund to support maintainers and contributors, administered by the Whitecore team. Void is bigger than VoidZero or Cloudflare, and the people who helped build it should be a part of what’s next.

The Vite and Cloudflare teams are already collaborating well ahead of this announcement, starting in 2024 white environment api. The Environment API lets Vite run server code in something other than Node.js during development. We worked closely with the White team on its design and then built it cloudflare white plugin On top of that.

when you run vite dev With the Cloudflare plugin, your server code runs in workerThe same open-source runtime that powers workers in production. Durable Objects, D1, KV, R2, Workflows, Workers AI, Agents, Service Bindings, Workers RPCs – they all run locally inside the same runtime model as production.

For a long time, the cost of developing on non-Node runtimes was that local development felt like a worse version of production. The Environment API removed that cost without forcing anyone to adopt a Cloudflare-specific dev server. Any runtime that wants to plug into Vite can do the same thing. That kind of design – a common mechanism across VITE with provider-specific implementation – has proven to work well and we want to keep it.

When we saw the adoption of the Cloudflare White plugin we knew we were onto something:

Vite’s adoption curve is one of the most remarkable things to see in the ecosystem right now. At the time of this writing, Vitae is roughly 129M weekly downloads. Cloudflare White Plugin (@cloudflare/vite-plugin) is approximately at 14M weekly downloads.

If you had told us a year ago that the Cloudflare White plugin would reach over 10% of White’s downloads, we wouldn’t have believed you. What happened? AI happened. More software is being created than ever before and most of it starts with AI-generated code. Those applications require a default stack and space to run. Agent-coded applications are choosing Vite, and increasingly they are choosing Vite running on Cloudflare.

Developers used to be the sole users of the dev server, bundler, linter, formatter, and CLI. This is no longer true: agents are also using them increasingly. They prepare the project, run the dev server, read errors, write tests, lint and format the code, deploy previews, and iterate.

A lot of AI-generated applications already start out as Vite apps, because Vite is fast, well-understood, and widely consistent with what agents have seen in their training data. Fast feedback loops have always been important. They become even more important when writing software with agents:

• Build faster, as they do more repetitions than humans.

• Fast testing, as they constantly re-run the suite to verify their own work.

• Faster lining up and formatting, because those tools become guardrails.

• Clear, structured errors, because the agent has to read and act on them.

• Consistent CLI, as small inconsistencies cause major disruptions.

The entire VoidZero toolchain is built around this type of loop. Witest, Rolldown, OxC, OxLint, and Oxfmt are each the fastest tools in their respective categories, and they work well when run repeatedly by an agent. Vite+ brings those pieces together into a CLI, a configuration model, and a toolchain with fewer moving parts. This makes it easier for people to understand the development loop, and easier for agents to drive reliably.

We’re dogfooding it ourselves. Cloudflare Dashboard is built on Vite. Oxlint is already there Saving days of engineering time In the Cloudflare codebase. gripAstro Team’s Agent Harness framework is also building on Waite as its foundation. Flu can run agents on Node.js, Cloudflare Workers, GitHub Actions, GitLab CI/CD, and more, and Cloudflare Targets now uses the official Cloudflare Vite plugin and worker integration. Vite is also becoming the default application foundation inside Cloudflare.

A few years ago, the job of a build tool was straightforward: take the source files, build a bundle, commit it. This is not enough for modern applications, especially in a world where some of those applications are agents themselves.

A modern application has server-rendered routes, APIs, background jobs, queues, databases, object storage, real-time, auth, plus agents and a growing list of AI capabilities. “Creation” is no longer the end of the story. This is the beginning of a deployment that requires understanding all of those parts.

This means that Vite has to become more than just a build tool. It needs to understand more about the application, while also staying true to what made Vette work in the first place: speed, simplicity, and portability.

voidA deployment platform designed for Vite has been another testing ground for these ideas. This helped to explore what a modern application framework should contain, what deployment should look like, and how much the full application lifecycle could be integrated around a toolchain. We have learned a lot from that work.

Now the work of putting those lessons in the right place is going on. Some are in the form of provider-agnostic primitives in Vite itself: first-class abstractions and hooks for backend, API, agents, and deployment that any provider can implement. Other lessons are inside Cloudflare. Cloudflare will provide a first-class implementation of those hooks across Workers and the rest of our developer platform.

Even though some wight maintainers are joining Cloudflare, changes to wight will continue to go through the same open contribution process as any other wight contribution. Features added to Vite themselves should not be Cloudflare-specific. They will also work where Witte works.

That same principle shaped how we thought about the future of Cloudflare’s own tooling. We are not moving Vite in the direction of Cloudflare. We’re doing the opposite: moving Cloudflare’s application tooling onto Vite, so it’s built on top of the same workflows that developers already know.

We recently sent a technical preview of cfA new unified CLI for the entire Cloudflare platform. Vite is going to be the basis of our CLI experience for applications. The end goal is a consistent CLI for all Cloudflare, with the same ergonomics whether you’re working on Workers, R2, D1, Agents, or anything else.

If we do this right, Cloudflare CLI should feel like wight, not like a separate thing stuck next to wight.

• cf dev must be a superset of vite dev. Same speed, same hot module replacement, same plugin model, plus Cloudflare runtime and bindings when you want them.

• cf build Vitae projects must be understood seamlessly, without the adapter dance.

• cf deploy This should make it simple to deploy Vite apps on Cloudflare.

If you’re running Vite today, the path to Cloudflare will feel like swapping in a superset of commands you already know. Same project size. Same white workflows. The entire Cloudflare developer platform is available when you want it.

In the short term, nothing changes for Vite users or the framework built on top of Vite:

• Vite, Vitest, Rolldown, Oxc, and Vite+ continue to ship. The VoidZero team continues to contribute and lead them.

• The Cloudflare Vite plugin keeps improving.

• The environment API and the broader story of “run your server code locally in the right runtime” is getting better, including non-Cloudflare runtimes.

Long Term:

• We begin work on moving the Cloudflare CLI to an experience built directly on top of Vite.

• Vite will get new, clean, provider-agnostic primitives for full-stack apps and agents that work for everyone, on any platform.

• Over time, we intend to open-source it void platformSo that others can learn from it and build their own platforms on top of Vyte and Cloudflare.

We will do all this publicly and with the community. The Vitae has always been built the same way.

Vite, Vitest, Rolldown, Oxc, and Vite+ exist because a deep ecosystem of open source contributors have put years of work into them. These projects are already at the heart of how the web is built, and we’re grateful to everyone who helped get them here. Thank you to everyone who contributed code, reviews, issues, documentation, plugins, integrations, and support during this time.

We’re excited to welcome the VoidZero team to Cloudflare, and look forward to putting more resources behind these projects. Our job now is to help them grow, stay open, and empower the JavaScript ecosystem for everyone.

Witte remains Witte. Cloudflare helps.

If you want to try Vite on Cloudflare today, run:

• npm create vite@latest

• npx wrangler deploy