Creator https://nitter.cf/t.co/HVzmuCcFfE / @vike_js ✦ Replaces Next.js/Nuxt ✦ 🔨 Composable framework to build advanced applications with flexibility and stability.
Germany, Munich
Joined March 2010
- Tweets1.3K
- Following10
- Followers1.5K
- Likes1.2K
> Vite remains vendor-neutral
Yes, and we're doubling down with new vendor-neutral APIs.
Collaborating:
- Vite (patak, @sapphi_red)
- Netlify (serhalp, @biilmann)
- Cloudflare (James Opstad, @MattieTK, @southpolesteve)
- Vike @vike_js / Universal Deploy (Joel)
Vite remains 💯
Today, VoidZero joins Cloudflare.
Vite remains MIT, vendor-neutral, and stewarded by the same wider team.
The same goes for Vitest, Rolldown, and Oxc.
Cloudflare is also committing $1M to an OSS fund to support independent development in the Vite ecosystem.
ALT Thumbnail of the blog post saying that Cloudflare supports Vite's mission
Great! 🚀
Hard to predict these things, but I'm optimistic Vite and VoidZero will stay mostly independent within Cloudflare.
Vite and VoidZero can now focus on building great tools ⚡️ without money-pressure from investors 🕊️
Today, VoidZero joins Cloudflare.
Vite remains MIT, vendor-neutral, and stewarded by the same wider team.
The same goes for Vitest, Rolldown, and Oxc.
Cloudflare is also committing $1M to an OSS fund to support independent development in the Vite ecosystem.
ALT Thumbnail of the blog post saying that Cloudflare supports Vite's mission
- What is Universal Deploy?
- Why Universal Deploy?
- Built-in Vike support via +server
- Collaboration with Vite team, Vite ecosystem, Tencent EdgeOne
More in the links above ⬆️
Thanks to everyone below for collaborating — it's what makes Open Source special 💚
@Netlify: serhalp (Philippe Serhal), @biilmann
@Cloudflare: James Opstad
@vite_js: Patak, @sapphi_red
@TencentCloudEO
Rom retweeted
The EdgeOne adapter for Vike has landed — and it ships with full Universal Deploy support from day one.
Deploy your Vike app with zero config, no platform-specific glue. The adapter reads everything it needs through Vike's UD protocol, so there's nothing to wire up by hand.
From there, one step takes your app to EdgeOne's worldwide edge network — served close to every user, everywhere.
See it in action⬇️
Very excited about the EdgeOne ⇄ Vike integration ✨
Tencent EdgeOne was among the first to believe in our Universal Deploy vision (official announcement coming soon) 💚
EdgeOne is quickly becoming a solid deployment choice 👀 CDN, edge network, streaming, ...
EdgeOne Pages now officially supports Vike framework @vike_js 🚀
SSR, SSG, and streaming — all running at the edge with a single edgeone/vite adapter.
We're also collaborating with the Vike team @brillout on Universal Deploy, the new framework-agnostic deployment standard for Vite.
Get started⬇️
ALT Introducing Vike Support on EdgeOne Pages
It really had a unique vibe.
I highly recommend going to React Paris! 🗼
🗼 #ReactParis 2026 - The #Aftermovie is here! 🎬
400+ #developers, 23 top-notch #speakers, 11 #sponsors, a world-class venue, a huge global #community support ... but ONE unforgettable, unique VIBE🤗. Our 3rd edition was our biggest and best yet. 🚀
Huge 🩵🤍❤️ to everyone who's made #Paris the center of the #React universe last month!
React C'est Magique!
React Paris 🗼 talk is live 🔴
Thank you @BeJS_ for this truly special conference fueled by a unique energy ✨
First time speaking in front of *so* many people. Loved it — and I can't wait to polish every aspect of my talk.
youtube.com/watch?v=gtRxhOna…
"Void Framework" is particularly interesting 👀
We're definitely up for contributing! 💚
The server functions demo is neat. End-to-end type safety (from DB to UI) is a big milestone for JS! It's a complex topic — we did a lot of design work in that space recently with Telefunc.
Introducing Void, the Vite-native deployment platform:
🚀 Full-stack SDK
⚙️ Auto-provisioned infra (db, kv, storage, AI, crons, queues...)
🔒 End-to-end type safety
🧩 React/Vue/Svelte/Solid + Vite meta-frameworks
🌐 SSR, SSG, ISR, islands + Markdown
🤖 AI-native tooling
☁️ One-command deploys
void.cloud
Can't wait to work on first-class integration with Void ✨🤩
Not only for Vike, but for any Vite-based framework via our work on Universal Deploy.
Introducing Void, the Vite-native deployment platform:
🚀 Full-stack SDK
⚙️ Auto-provisioned infra (db, kv, storage, AI, crons, queues...)
🔒 End-to-end type safety
🧩 React/Vue/Svelte/Solid + Vite meta-frameworks
🌐 SSR, SSG, ISR, islands + Markdown
🤖 AI-native tooling
☁️ One-command deploys
void.cloud
Today's announcement is a pivotal day for Vite and VoidZero's future.
I can't way 👀 feels like Apple's unveiling back in the iPhone days.
👀 👀 👀
ALT "A dark-themed code editor showing three JavaScript import statements. The first imports defineConfig from a partially pixelated module name starting with "vi", the second imports a pixelated export name starting with "v" from a pixelated module also starting with "v", and the third reads import { evan } from "@vuejs/amsterdam".
It's always a pleasure interacting with @sapphi_red — reliable, insightful, helpful — sometimes even contributing PRs to Vike.
Vite's care for its ecosystem is truly remarkable.
Big shoutout to @sapphi_red for leading, pushing and coordinating this huge effort. Truly one of the most amazing engineers I have worked with.
Rom retweeted
@voidzerodev will be releasing a lot of new stuff this week. Follow us if you don’t want to FOMO.
Great to see Vercel and Cloudflare collaborating on streaming infrastructure.
That's the kind of collaboration we're working towards with the Photon project (next-gen integration of deployment providers & JS servers).
Huge fan of James Snell's work on New Streams github.com/jasnell/new-strea…
2 weeks ago we shared how WebStreams could be much faster on the server. But staying within the current spec can only get so far while staying 100% compatible. James is introducing a new API which
- Allows for *much* faster implementations
- It's frankly a more idiomatic API for the modern TypeScript ecosystem
It's worth making the current API faster because it is so broadly deployed, but we also need a good long term path and this is it.
I'd also like to comment on how with all the drama you see here, this is how things actually work behind the scenes.
@matteocollina connected James and me because he knew that both us were working on making streams faster. I reviewed James' proposal and he reviewed our faster WebStreams implementation before they shipped. Huge thanks to @Cloudflare for sponsoring James' work on this.
This is very similar to what is happening with Next.js which is currently in the final phases of shipping a new adapter API for making it easier for Next.js to be deployed. Behind the scenes employees from all relevant companies are collaborating on this in a super chill and trusted manner.
