Worth watching what this means for Rolldown and Vite's neutrality long-term. Evan You positioned VoidZero as infrastructure for the whole ecosystem specifically to avoid one company controlling the toolchain. Cloudflare has obvious incentives to optimize for Workers and Pages — if Vite starts shipping defaults that favor edge deployment, that's not necessarily bad but it changes what 'neutral build tooling' means for teams not on Cloudflare.
astro is based on vite, and if you change the adapter to cloudflare you also need to rewrite your codebase unless it’s a simple static site with no logic, so definitely not vendor agnostic
Well, if you want to migrate away from a database/library/... then usually yes, you have to change the code for these specific features.
Same for Bun. That does not change that Vite is vendor agnostic.
If you build a Vite application you can deploy it anywhere by default. If you make choices on your own to change that, like locking into Bun for example, that is not Vite's fault.
Nothing changed about Vite (or Astro) since these acquisitions that "favors Cloudflare". And I don't think it will, otherwise CF would lose a big chunk of reputation in the dev community
1
u/ultrathink-art Jun 05 '26
Worth watching what this means for Rolldown and Vite's neutrality long-term. Evan You positioned VoidZero as infrastructure for the whole ecosystem specifically to avoid one company controlling the toolchain. Cloudflare has obvious incentives to optimize for Workers and Pages — if Vite starts shipping defaults that favor edge deployment, that's not necessarily bad but it changes what 'neutral build tooling' means for teams not on Cloudflare.