The Next.js API surface, re-implemented on Vite

Run your Next.js app on Vite. Deploy anywhere.

Vinext is a Vite plugin that re-implements the Next.js API from scratch. Keep your app/, pages/, and next.config.js as they are. Get a faster dev loop, smaller bundles, and a clean path to deploy on any host.

Get vinext on GitHub Read the announcement

Up to 4×

faster production builds

Measured against Next.js 16 with Turbopack on a 33-route App Router benchmark app.

~50%

smaller client bundles

168.9 KB → 72.9 KB gzipped on the same benchmark. Tree-shaking and a lighter client runtime do the work.

94%

of the Next.js 16 API surface

App Router, Pages Router, RSC, server actions, ISR, middleware, route handlers. Coverage and gaps tracked openly.

Benchmarks are directional, not definitive. See the launch numbers and methodology in the announcement.

The same framework, on a different foundation

Vinext re-implements Next.js as a Vite plugin instead of wrapping its build output. That single decision unlocks a faster toolchain and a much wider set of deployment targets.

Drop-in Next.js

Keep your existing app/, pages/, and next.config.js. The full Next.js 16 API surface is shimmed — App Router, Pages Router, RSC, server actions, ISR, middleware, and the next/* module imports you already use.

Powered by Vite

Fast HMR, native ESM, and the Vite plugin ecosystem. Built on @vitejs/plugin-rsc for React Server Components, and ready for Rolldown — the Rust-based bundler shipping in Vite 8.

Deploy anywhere

Cloudflare Workers is the first deployment target, with one-command deploys via vinext deploy. Vercel, Netlify, AWS, Deno Deploy, and more, work through Nitro, and standalone Node bundles are emitted on demand.

Production features, ready to go

Caching, bindings, image optimization, and pre-rendering all work out of the box on Cloudflare Workers, with sensible defaults you can swap out when you need to.

Platform bindings in your app code

Import env from cloudflare:workers directly inside server components, route handlers, and server actions. Bindings work in dev and production with no proxy layer.

ISR out of the box

Stale-while-revalidate with background regeneration, matching the Next.js 16 CacheHandler interface. A KV-backed handler ships by default; R2 or your own backend can drop in.

Traffic-aware Pre-Rendering

Experimental

Pre-render only the pages real traffic hits, using zone analytics at deploy time. Popular pages get SSG-level latency without building tens of thousands of routes ahead of time.

Image optimization

Local images route through a runtime resize/transcode endpoint that integrates with the Cloudflare Images binding. Remote images use @unpic/react with auto-detection for 28 CDNs.

See it running

Real Next.js apps, rebuilt on every push to main and deployed to Cloudflare Workers. Source is on GitHub.

App Router Playground

Vercel's official Next.js App Router Playground, running on vinext. Covers the breadth of App Router features — server components, parallel routes, streaming, error boundaries, metadata.

Hacker News

RSC-first Hacker News clone with streaming, nested layouts, and server actions. A good look at what an idiomatic vinext app feels like end to end.

Migrate in one command

npx vinext init scans your project for compatibility issues, installs the right dependencies, generates a Vite config, and adds vinext scripts alongside your existing Next.js setup. It's non-destructive — next dev keeps working.

Read the quick start Migration guide

vite.config.ts

Configure vinext in Vite

Start with the vinext plugin, then add the adapter for your deployment target. Your routes, components, and Next.js configuration stay exactly where they are.

Start with vinext

The smallest config for running a Next.js app through Vite.

vite.config.ts

import { defineConfig } from "vite";
import vinext from "vinext";

export default defineConfig({
  plugins: [vinext()],
});

Deploy to Cloudflare Workers

Add the Cloudflare Vite plugin, Workers KV caching, and Cloudflare Images optimization.

vite.config.ts

import { cloudflare } from "@cloudflare/vite-plugin";
import { kvDataAdapter } from "@vinext/cloudflare/cache/kv-data-adapter";
import { imagesOptimizer } from "@vinext/cloudflare/images/images-optimizer";
import { defineConfig } from "vite";
import vinext from "vinext";

export default defineConfig({
  plugins: [
    vinext({
      cache: {
        data: kvDataAdapter(),
      },
      images: {
        optimizer: imagesOptimizer(),
      },
    }),
    cloudflare({
      viteEnvironment: {
        name: "rsc",
        childEnvironments: ["ssr"],
      },
    }),
  ],
});

Or deploy with Nitro

Use Nitro when you want adapters for Node, Vercel, Netlify, AWS, and more.

vite.config.ts

import { nitro } from "nitro/vite";
import { defineConfig } from "vite";
import vinext from "vinext";

export default defineConfig({
  plugins: [vinext(), nitro()],
});