vinext
vinext reimplements the Next.js API surface on Vite. Your app/, pages/, next.config.js, and public/ stay as-is; the compiler toolchain underneath is replaced. Cloudflare built it as an experiment in AI-driven development (announced March 2026) and it is the third path for Next.js apps on the platform, between OpenNext (adapting next build output) and a full rewrite.
Status: experimental, by design
Cloudflare’s own framing is blunt: experimental, under heavy development, mostly AI-written code with humans directing architecture. Two numbers matter:
- ~94% of the Next.js API surface works. The missing slice is the long tail that depends on undocumented Vercel behavior, intentionally unsupported
- Targets Next.js 16.x only. Deprecated APIs from older Next versions will not work
It is not a fork: the core is written from scratch on Vite (@vitejs/plugin-rsc provides RSC). App Router builds run multi-environment (RSC + SSR + client).
How it differs from OpenNext
| OpenNext | vinext | |
|---|---|---|
| Approach | Adapts next build output | Reimplements Next.js APIs on Vite |
| API coverage | Broadest (inherits Next.js output) | ~94%, long tail excluded |
| Maturity | Years in production | Experimental (2026-03) |
| Build/bundle | Next.js toolchain | Faster builds, smaller bundles |
| Deploy targets | AWS, Cloudflare, Netlify | Cloudflare Workers native; others via Nitro |
| When | Safer, proven, more coverage | Lighter toolchain, Cloudflare-first, can tolerate rough edges |
vinext’s own README says this plainly: OpenNext is the safer choice for mature coverage; vinext is worth a look if you want the lighter toolchain and don’t need every Next.js API.
The migration story
vinext ships an agent skill (npx skills add cloudflare/vinext) plus a non-destructive CLI migration: vinext init runs vinext check (compatibility scan), installs deps, adds scripts, and generates a minimal vite.config.ts. Your Next.js setup keeps working side by side (npm run dev vs npm run dev:vinext), and nothing in next.config, tsconfig.json, or source files is modified.
Honest fit assessment
Good fit: Cloudflare-first apps on recent Next.js that want Vite’s toolchain, accept experimental risk, and don’t lean on the API long tail.
Poor fit: anything needing guaranteed API coverage, older Next.js versions, or production risk aversion. For those: OpenNext (keep coverage) or a rewrite to a native framework (see Landscape).