Vinext 1.0: Next.js on Vite reaches production readiness

Vinext is Cloudflare's reimplementation of the Next.js web framework on top of Vite, a different build tool, so that an existing Next.js application can be deployed to any web platform, including the Cloudflare Workers free plan, Netlify or AWS Lambda. It began in February as what Cloudflare calls a week-long, AI-driven experiment in how far one engineer and a stack of tokens could get at replicating Next.js. With version 1.0, Cloudflare says customers now run it in production for high-traffic, dynamic applications.

The hard part of a reimplementation is matching behavior, and that is what the 1.0 label rests on. Cloudflare's example is revalidatePath: writing a function with that name is simple, but it must also update the rendered pages, the cache entry and later requests exactly as Next.js would. Cloudflare reports test compatibility above 99% for the most important customer-requested features, across both of Next.js's routing systems, the App Router and the Pages Router that many large, hard-to-migrate applications still use. It tracks this with thousands of its own tests and a nightly run of the Next.js end-to-end test suite against Vinext. One gap is deliberate: support for the "use cache" directive behind Next.js 16's Cache Components is limited, because most teams Cloudflare talked to were not using them.

The main new capability is cache warming. Next.js applications can render pages during the build and then refresh them with Incremental Static Regeneration, which serves a stored page and regenerates it in the background or on demand. Vinext 1.0 supports that cycle, but Cloudflare argues that a site with tens or hundreds of thousands of URLs wastes hours rendering pages that get little traffic. With cache warming, a new version is deployed to 0% of production traffic, pages are requested from that version to fill Cloudflare's cache, and only then is it promoted, so the first real visitors get cached responses. Vinext can also add high-traffic pages to the list developers mark for prerendering.

Keeping up with Next.js is now largely handed to agents. Each morning an agent reviews new commits to Next.js canary and opens tracking issues for anything that could affect Vinext; each night the compatibility matrix is regenerated, and when a gap appears agents can build a reproduction, port tests and propose a fix. That leaves maintainers the cases that need judgment about how Next.js behavior should map onto Vite. The 99% figure is Cloudflare's own measurement, and the two migration commands, npx vinext check and npx vinext init, are how a team verifies its own application before switching.