vinext

Overview

vinext runs Next.js applications on Vite, with Cloudflare Workers as its primary deployment target. Instead of adapting the output of next build, it reimplements the Next.js API surface on top of Vite — so you keep writing Next.js code (App Router or Pages Router) while gaining Vite’s fast dev server and a first-class path to the edge.

The project is under active development: it already supports substantial Next.js applications, but it is not yet a drop-in replacement for every app, so it is worth checking compatibility before migrating.

What Works Today

• App Router and Pages Router in development and production builds
• React Server Components, Server Actions, route handlers, and middleware
• Static generation, ISR, static export (output: "export"), and standalone Node.js output
• Core Next.js modules such as next/link, next/image, next/navigation, next/headers, next/cache, and the Metadata API
• Cloudflare Workers deployment with bindings, cache adapters, and on-demand image optimization
• Migration tooling: vinext check, vinext init, and an Agent Skill for AI coding tools

Known Gaps

Some areas are still in progress, including full Cache Components / Partial Prerendering behavior, build-time image and font optimization, and certain native modules during App Router development. Run vinext check against your app to see what applies.

Getting Started

Create a new project:

pnpm create vinext-app@latest my-app

Or migrate an existing Next.js app in place:

npx vinext init

Then develop and deploy with Vite:

npx vite dev                    # dev server with HMR
npx vite build                  # production build
npx @vinext/cloudflare deploy   # build and deploy to Cloudflare Workers

Why It Matters

vinext gives teams with existing Next.js codebases a way to deploy to Cloudflare Workers without rewriting their app, while moving the toolchain onto Vite.

License

MIT License.