VoidZero Is Joining Cloudflare

VoidZero 加入 Cloudflare

VoidZero, the company behind Vite, Vitest, Rolldown, Oxc, and Vite+, is joining Cloudflare. As part of this change, all team members of VoidZero are joining Cloudflare, too. VoidZero——Vite、Vitest、Rolldown、Oxc 和 Vite+ 背后的公司——现已加入 Cloudflare。作为此次变动的一部分，VoidZero 的所有团队成员也将加入 Cloudflare。

Before saying anything else, we want to make the most important thing clear: Vite, Vitest, Rolldown, Oxc, and Vite+ will stay open source, vendor-agnostic, and community-driven. Nothing about that changes. 在谈论其他事情之前，我们想先明确最重要的一点：Vite、Vitest、Rolldown、Oxc 和 Vite+ 将继续保持开源、与供应商无关且由社区驱动。这一点不会有任何改变。

Cloudflare’s mission is to help build a better Internet. And a better Internet is an open Internet. Developers need choice, frameworks need a neutral foundation, and applications need to be portable. It is not reasonable to expect the entire web ecosystem to build around a single vendor. The most important tools and frameworks are portable by design. Cloudflare 的使命是助力构建一个更美好的互联网。而一个更美好的互联网必然是开放的互联网。开发者需要选择权，框架需要中立的基础，应用程序需要具备可移植性。期望整个 Web 生态系统围绕单一供应商构建是不合理的。最重要的工具和框架在设计之初就应具备可移植性。

Vite is one of the few foundational tools that the whole JavaScript ecosystem agrees on. It earned that position by being fast, excellent, portable, and vendor-neutral. One of the best ways Cloudflare can help build a better Internet is by investing in that foundational open source toolchain. A toolchain that makes the Internet better for everyone, not just people who use Cloudflare or choose to host with us. Vite 是整个 JavaScript 生态系统中为数不多达成共识的基础工具之一。它凭借快速、卓越、可移植和供应商中立的特性赢得了这一地位。Cloudflare 助力构建更美好互联网的最佳方式之一，就是投资于这一基础开源工具链。这套工具链旨在让互联网对每个人都变得更好，而不仅仅是针对那些使用 Cloudflare 或选择托管在我们平台上的用户。

Over the last few years we’ve invested heavily in making Cloudflare the best place to build and run websites, applications, and agents on our developer platform. But ultimately that choice will always be yours. Run your Vite application anywhere you want. 在过去的几年里，我们投入了大量资源，致力于将 Cloudflare 打造为在我们的开发者平台上构建和运行网站、应用程序及智能体的最佳场所。但归根结底，选择权永远在你们手中。你们可以在任何地方运行自己的 Vite 应用程序。

What this means for Vite

这对 Vite 意味着什么

Today’s news gives Vite more resources to keep growing, while the things that make Vite what it is remain the same: 今天的新闻为 Vite 提供了更多持续发展的资源，同时让 Vite 保持其核心特性的因素将保持不变：

Vite remains MIT-licensed and open source.
Vite 继续保持 MIT 许可并开源。
Vite remains vendor-agnostic. Applications built with Vite run anywhere and will continue to do so.
Vite 继续保持与供应商无关。使用 Vite 构建的应用程序可以在任何地方运行，未来也将如此。
Vite’s roadmap continues to be driven by the broader Vite team and community, and continues to be developed in the open.
Vite 的路线图继续由更广泛的 Vite 团队和社区推动，并继续在公开环境下进行开发。
Evan and the rest of the VoidZero team continue to lead Vite, Vitest, Rolldown, Oxc, and Vite+.
Evan 和 VoidZero 团队的其他成员将继续领导 Vite、Vitest、Rolldown、Oxc 和 Vite+。
Cloudflare is committing engineering and resources to those projects, not redirecting them.
Cloudflare 致力于为这些项目投入工程力量和资源，而不是改变它们的方向。

We made the same kind of commitment when Astro joined Cloudflare earlier this year. Astro is still open source, and still deploys anywhere. The team is still shipping the roadmap they were already shipping. 今年早些时候 Astro 加入 Cloudflare 时，我们也做出了同样的承诺。Astro 依然开源，依然可以部署在任何地方。团队依然在按原定路线图推进开发。

This commitment matters even more with Vite, because Vite is not one framework. Vite is the foundation underlying so many: Vue, SvelteKit, Nuxt, Astro, Solid, Qwik, Angular, React Router, TanStack Start. Even Next.js now has a Vite-based implementation in vinext. Vite has become a shared foundation for the JavaScript ecosystem. Our number one goal is to maintain the trust that has earned Vite so much adoption. Not with our words here, but by proving it every day in how we support and develop these projects. 对于 Vite 而言，这种承诺显得尤为重要，因为 Vite 不仅仅是一个框架。Vite 是众多框架的底层基础：Vue、SvelteKit、Nuxt、Astro、Solid、Qwik、Angular、React Router、TanStack Start 等等。甚至 Next.js 现在也有了基于 Vite 的实现（vinext）。Vite 已成为 JavaScript 生态系统的共同基础。我们的首要目标是维护 Vite 赢得如此广泛采用的信任。我们不会仅仅停留在口头承诺上，而是会通过每天支持和开发这些项目的实际行动来证明这一点。

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 committing $1 million to a Vite ecosystem fund to support maintainers and contributors, administered by the Vite core team. Vite is bigger than VoidZero or Cloudflare, and the people who have helped build it should be part of what comes next. 在支持开源和共享生态系统基础方面，我们也希望言行一致。作为此次公告的一部分，Cloudflare 将向 Vite 生态系统基金投入 100 万美元，用于支持维护者和贡献者，该基金将由 Vite 核心团队管理。Vite 的意义远超 VoidZero 或 Cloudflare，那些帮助构建它的人应当成为未来发展的一部分。

Vite as the foundation

Vite 作为基础

The Vite and Cloudflare teams have been collaborating well before this announcement, starting in 2024 with the Vite Environment API. The Environment API lets Vite run server code in something other than Node.js during development. We worked closely with the Vite team on its design, and then built the Cloudflare Vite plugin on top of it. 在本次公告发布之前，Vite 和 Cloudflare 团队就已经进行了良好的合作，始于 2024 年的 Vite Environment API。Environment API 允许 Vite 在开发过程中在 Node.js 之外的环境中运行服务器代码。我们与 Vite 团队密切合作设计了该 API，并在此基础上构建了 Cloudflare Vite 插件。

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 – all of it runs locally inside the same runtime model as production. 当你使用 Cloudflare 插件运行 vite dev 时，你的服务器代码会在 workerd 中运行，这与生产环境中驱动 Workers 的开源运行时是同一个。Durable Objects、D1、KV、R2、Workflows、Workers AI、Agents、Service Bindings、Workers RPC——所有这些都在本地以与生产环境相同的运行时模型运行。

For a long time, the cost of developing on a non-Node runtime was that local dev 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 generic mechanism in Vite with provider-specific implementations – has proven to work well and is one we want to keep building on. 长期以来，在非 Node 运行时上开发的代价是本地开发体验往往不如生产环境。Environment API 消除了这一代价，且无需强迫任何人采用 Cloudflare 特定的开发服务器。任何想要接入 Vite 的运行时都可以实现同样的功能。这种设计——即 Vite 中的通用机制配合特定提供商的实现——已被证明非常有效，也是我们希望继续深耕的方向。

We knew we were on to something when we saw adoption of the Cloudflare Vite plugin take off: Vite’s adoption curve is one of the more remarkable things to watch in the ecosystem right now. As of this writing, Vite is at roughly 129M weekly downloads. The Cloudflare Vite plugin (@cloudflare/vite-plugin) is at almost 14M weekly downloads. 当我们看到 Cloudflare Vite 插件的采用率激增时，我们就知道我们做对了：Vite 的采用曲线是目前生态系统中值得关注的最显著现象之一。截至撰写本文时，Vite 每周下载量约为 1.29 亿次。Cloudflare Vite 插件 (@cloudflare/vite-plugin) 每周下载量已接近 1400 万次。

If you had told us a year ago that a Cloudflare Vite plugin would reach downloads equivalent to more than 10% of Vite itself, we wouldn’t have believed you. What happened? AI happened. More software is being created than ever before, and a lot of it starts with AI-generated code. Those applications need a default stack and a place to run. Agent-coded applications are choosing Vite, and increasingly they are choosing Vite running on Cloudflare. 如果一年前有人告诉我们，Cloudflare Vite 插件的下载量将达到 Vite 本身下载量的 10% 以上，我们是不会相信的。发生了什么？AI 发生了。现在创造的软件比以往任何时候都多，其中很多都是从 AI 生成的代码开始的。这些应用程序需要一个默认的技术栈和一个运行的地方。由智能体（Agent）编写的应用程序正在选择 Vite，并且越来越多地选择在 Cloudflare 上运行 Vite。

AI is changing how we write software

AI 正在改变我们编写软件的方式

Developers used to be the only users of dev servers, bundlers, linters, formatters, and CLIs. That is no longer true: agents are using them too, constantly. They scaffold projects, run dev servers, read errors, write tests, lint and format code, deploy previews, and iterate. 过去，开发者是开发服务器、打包工具、代码检查工具、格式化工具和 CLI 的唯一用户。现在情况变了：智能体也在不断地使用它们。它们负责搭建项目、运行开发服务器、读取错误信息、编写测试、检查和格式化代码、部署预览以及进行迭代。

A lot of AI-generated applications already start as Vite apps, because Vite is fast, well understood, and broadly compatible with what agents have seen in their training data. Fast feedback loops have always been important. They become even more critical when writing software with agents: 许多 AI 生成的应用程序已经以 Vite 应用的形式起步，因为 Vite 速度快、易于理解，并且与智能体在其训练数据中看到的内容广泛兼容。快速反馈循环一直很重要。而在使用智能体编写软件时，这一点变得更加关键：

Fast builds, because they iterate more than humans do.
快速构建，因为它们的迭代频率远高于人类。
Fast tests, because they re-run the suite constantly to verify their own work.
快速测试，因为它们会不断重新运行测试套件来验证自己的工作。
Fast linting and formatting, because those tools become guardrails.
快速检查和格式化，因为这些工具成为了代码质量的护栏。
Clear, structured errors, because the agent has to read and act on them.
清晰、结构化的错误信息，因为智能体必须读取并根据这些信息采取行动。
Consistent CLIs, because small inconsistencies…
一致的 CLI，因为微小的不一致性……