Next.js applications, powered by Vite: introducing Vinext 1.0

Cloudflare has released Vinext 1.0, the Vite-backed framework first launched in February as a week-long experiment by one engineer to replicate Next.js on top of Vite. Since then it has been used in production for high-traffic dynamic applications, and the 1.0 release covers compatibility, stability and caching improvements.

Vinext takes a Next.js application built for either the Pages or App Router and makes it portable across web platforms, including the Cloudflare Workers free plan, Netlify and AWS Lambda. Compatibility for most important customer-requested features now surpasses 99%, a figure the source notes excludes cache components.

Support spans both routing paths and hybrid apps, covering React Server Components, Server Actions, API routes, route handlers, middleware and client-side navigation. The page lifecycle includes server rendering, build-time prerendering, static export via output: "export", and page-level Incremental Static Regeneration (ISR), where background and on-demand revalidation work with any output. Vinext provides shared caching functions across routers and runtimes plus Cloudflare Workers Cache support, and Next.js-compatible tracing keeps existing OpenTelemetry and Sentry setups working. It implements the public next/* surface and common Next patterns for authentication, MDX, image optimization, fonts, metadata and environment variables. Server code can run in Cloudflare's workerd runtime with access to bindings such as image optimization and hyperdrive.

Migration uses two commands, npx vinext check and npx vinext init. On Cache Components, driven by the "use cache" directive, support remains limited; the source says most teams it spoke with did not treat it as a prerequisite to move.

A new cache warming feature moves prerendering off the build machine to Cloudflare's network, using generateStaticParams() and getStaticPaths() to identify pages and adding high-traffic pages. It uploads a new Worker version at 0% of production traffic, requests pages from that version to populate caches, then promotes the deployment. Deploying with warming uses npx @vinext/cloudflare deploy --warm-cache.

Why it matters: Teams can run existing Next.js apps, including Pages Router projects, on Cloudflare Workers, Netlify or AWS Lambda, and check compatibility before migrating.