Cloudflare buys VoidZero, keeps Vite open-source — and here is the real reason why

Cloudflare has acquired VoidZero, the small team behind Vite, the JavaScript build tool that nearly every modern framework now depends on. Evan You, creator of both Vue.js and Vite, is moving into Cloudflare, along with the rest of the VoidZero crew. The catch, as always with "acqui-hires", is what happens to the open-source projects: Vite, Vitest, Rolldown, Oxc, and Vite+ will stay open-source, vendor-agnostic, and community-driven. Cloudflare is also pledging $1 million to a Vite ecosystem fund administered by the core team.

On the surface this reads like a generous move — Cloudflare, the DDoS-protection-and-DNS company, is buying the team that built the single most universally-accepted frontend toolchain in the JavaScript ecosystem and promising not to change anything. The detail that matters, though, is the Vite Environment API. Worked on jointly since 2024, it lets Vite run server code in something other than Node.js during development — which means running server code inside Cloudflare's own workerd runtime. The Cloudflare Vite plugin already exists. The acquisition accelerates that path: Vite developers now run inside Cloudflare's infrastructure by default, while still being able to deploy anywhere. It's the same playbook they used when Astro joined earlier this year — acquire the team, keep the project neutral, quietly make Cloudflare the easiest place to build.

Source article image
Source image 1

HN is split in the way you'd expect. Some see it as the natural endgame for open-source projects that never found a revenue model — build a popular tool, raise VC money, get acquired by a platform company that happens

Source article image
Source image 2
to share your investor slate. Others point out that the $1 million ecosystem fund is a real commitment, not just press-release language. The question isn't whether Vite will survive — it'll be fine — but whether Cloudflare's version of "neutral" holds up when a future Vite feature only makes sense on their platform. Evan You has earned trust; he's also running a company now.

Sources

Comments

Post a Comment

Popular posts from this blog

AI Is Starting to Feel Less Like a Gadget and More Like Infrastructure

Image
Modern AI doesn't replace infrastructure — it runs on top of it. (Photo: Unsplash) For a while, AI coverage had the energy of a mall demo kiosk: very shiny, slightly chaotic, and usually one prompt away from embarrassment. Lately, though, the more interesting story is less about flashy demos and more about infrastructure. A useful CNBC piece argued that AI is not simply going to vaporize enterprise software overnight, and that sounds about right. In real companies, software does not disappear just because a model can summarize a meeting or write a decent SQL query. What actually happens is messier and more practical: AI starts sneaking into the plumbing. It shows up in search, support workflows, procurement tools, analytics dashboards, and data pipelines. The real winners may not be the loudest chatbot wrappers, but the vendors that make enterprise systems easier to operate, easier to query, and slightly less soul-crushing for the humans trapped inside them. That is less cinematic ...
Read more

When Two AI Bots Finally Learned to Talk in Discord

I spent part of the day doing something that sounds like the setup for a bad joke: getting two local AI assistants to talk to each other in the same Discord channel. Not through a web UI. Not by bouncing prompts manually between windows like a human message queue. In the actual shared channel, where both could see the conversation and react to each other. The funny part is that the problem was not intelligence. It was manners. Both bots were defensive by default around bot-authored messages, which is the sensible setting if you do not want your infrastructure turning into a recursive support group. The downside is obvious: if both assistants treat other bots as suspicious background noise, they will never coordinate on anything more useful than silence. The fix was to make both sides accept bot-authored messages only when they were explicitly mentioned. That detail matters more than it sounds. Blanket bot acceptance is how you end up with two enthusiastic systems discovering each oth...
Read more

A CISA Contractor's GitHub Repo Held 844 MB of Secrets — and No One Closed the Door

Image
There is something almost poetic about the US government's premier cybersecurity agency — the one whose job is literally to plug holes in critical infrastructure — getting outsmarted by a contractor who treated a public GitHub repository like a digital junk drawer. The "Private-CISA" repo, created November 13, 2025, sat publicly for six months containing 844 megabytes of plaintext passwords, AWS GovCloud administrative credentials, Kubernetes manifests, ArgoCD application files, Terraform infrastructure code, CI/CD build logs, and internal deployment documentation. Guillaume Valadon at GitGuardian flagged it on May 14 after his automated scanning picked up the exposure. The commit history told the whole story in plain sight: the account owner had explicitly disabled GitHub's default secret-scanning protections, pushed plaintext credentials stored in CSV files, committed full backup archives into git history, and used easily guessed passwords like "platform-name-2...
Read more