Next.js applications, powered by Vite: introducing Vinext 1.0
- ID
- 29329
- Status
- summarized
- Published
- 28 Sep 2026, 10:51 PM
- Fetched
- 28 Sep 2026, 11:42 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/vinext-nextjs-on-vite/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 7.0
- Created
- 28 Sep 2026, 11:42 PM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Cloudflare released Vinext 1.0, a Vite-based runtime that runs existing Next.js apps (both Pages and App Router) and deploys them to Cloudflare Workers' free plan, Netlify, or AWS Lambda. It began in February as a week-long AI-driven experiment and now reports over 99% test compatibility with Next.js, excluding cache components. Migration is two commands: `npx vinext check` and `npx vinext init`.
Why it matters
If you run Next.js on Vercel and your bill or platform lock-in is a concern, this is a concrete escape hatch with a measurable compatibility claim you can test on your own repo in minutes via `npx vinext check` before committing to anything. The honest caveat is the one that matters most: the 99% figure excludes cache components, and the post itself admits replicating cache entry, rendered page, and future-request behavior around things like `revalidatePath` was the hardest part — so ISR/revalidation-heavy apps are exactly where you should verify manually rather than trust the number.
Discussion angle
Run `npx vinext check` live on a real Next.js project and look at what it flags — then debate whether a Cloudflare-maintained Next.js reimplementation is a safer bet than Vercel lock-in, given that the project's own authors say matching Next.js cache semantics, not the API surface, was the hard part.