Next.js apps on Vite: Cloudflare ships Vinext 1.0

Cloudflare released Vinext 1.0, a framework that lets any Next.js application run on Vite. The company announced the release on its blog on September 28, 2026.

From an AI experiment to production

Vinext began in February as a week-long, AI-driven experiment to find out how far one engineer could get in replicating the Next.js framework on top of Vite. Seven months later, Cloudflare says the project has grown into a framework that customers run in production for high-traffic, dynamic applications.

Version 1.0 focuses on portability: an application built for either the Pages or the App Router can be deployed to any web platform, including the Cloudflare Workers free plan, Netlify, or AWS Lambda. According to Cloudflare, test compatibility for the features customers request most now surpasses 99%, excluding cache components.

What's in 1.0

The release supports both routers and hybrid applications, covering React Server Components, Server Actions, API routes, route handlers, middleware, and client-side navigation. Pages can be rendered on the server, pre-rendered during the build, exported as static assets, or cached with page-level Incremental Static Regeneration (ISR). Background and on-demand revalidation work with any output.

Caching functions are shared across the App and Pages Router and the supported runtimes, with additional support for Cloudflare's Workers Cache. Tracing stays compatible with Next.js, so existing OpenTelemetry and Sentry setups keep working, and traces on Workers integrate with native Workers Observability. Vinext implements the public next/* surface and common Next.js patterns for authentication, MDX, image optimization, fonts, and metadata.

Cache warming

Vinext previously supported ISR only after the first request. Version 1.0 can prerender routes during the build using generateStaticParams() and getStaticPaths(), invalidate those responses by path or tag, and also supports a fully static export.

Because large sites can spend hours rendering hundreds of thousands of low-traffic URLs, Cloudflare introduced cache warming. Page prerendering moves from the build machine to Cloudflare's network, which can additionally pick out high-traffic pages. A new Worker version is uploaded and deployed to 0% of production traffic, pages are requested from it, and the deployment is promoted once the caches are populated.

What's next

Each morning, agents review commits to the Next.js canary and open tracking issues for changes that could affect Vinext; every night the compatibility matrix is regenerated. Migration takes two commands, npx vinext check and npx vinext init. New projects start with npm create vinext-app@latest my-app, and deployment uses npx @vinext/cloudflare deploy --warm-cache. Vinext is open source at github.com/cloudflare/vinext.