Docs/Overview
Docs/Quickstart/Vinext (V8 Isolate)

Vinext on Exovon

Run Next.js applications on Vite and deploy them to Exovon's zero-cold-start V8 Isolate runtime. Enjoy the full power of Next.js App Router, React Server Components (RSC), and Server Actions with sub-5ms invocations, fast local dev builds, and reduced memory overhead.

Why Vinext on Exovon?

Next.js has become the industry standard for React full-stack engineering, but standard Node.js container builds can be resource-heavy. Vinext pairs Next.js with Vite and V8 Isolates for immediate responsiveness.

Sub-5ms V8 Isolate Cold Starts

Instead of booting an entire Linux container with Docker and Node.js runtime overhead, Exovon runs Vinext apps inside lightweight V8 Isolates (workerd). Cold boots drop from seconds to single-digit milliseconds.

Vite Engine & Instant HMR

Vinext replaces Webpack and Turbopack with Vite's native Rollup/esbuild toolchain. Local development servers start in under 300ms with instant Hot Module Replacement (HMR).

Reduced Memory Footprint

Because V8 Isolates share the underlying host runtime without container virtualization layers, Vinext apps consume as little as 15–30 MB of RAM under load.

Deterministic Sandboxing

Every tenant executes inside an isolated memory heap. Code within one isolate cannot inspect or affect another isolate, guarded by isolated memory boundaries and strict execution watchdog timers.

How Exovon Executes Vinext

Exovon provides a dedicated build and execution pipeline engineered specifically for Vinext and V8 isolate runtimes:

1

Automated Preflight

When you deploy via GitHub or the CLI, our preflight analyzer checks your package.json. If vinext is detected, Exovon assigns your build to the v8-isolate pipeline.

2

Vite Compilation

Exovon executes vinext build inside an isolated runner. The compiler outputs a standalone worker bundle (dist/worker.js) and static client assets.

3

V8 Isolate Dispatch

The bundle is deployed to Exovon's V8 Isolate engine. Inbound requests are executed in sub-5ms with zero cold start delays.

Getting Started: Creating or Migrating

Scaffold a new Vinext application or convert an existing Next.js App Router project:

Create a New Vinext App

Run the creator CLI to scaffold a modern Next.js 16 + Vite project with TypeScript and Tailwind CSS:

Terminal
npm create vinext@latest my-vinext-app
cd my-vinext-app
npm install
npm run dev

Core Configuration Files

Vinext integrates via standard Vite configuration:

vite.config.ts
import { defineConfig } from 'vite';
import vinext from 'vinext';

export default defineConfig({
  plugins: [
    vinext()
  ],
  build: {
    target: 'esnext',
    outDir: 'dist'
  }
});

Next.js Feature Compatibility

Write idiomatic Next.js App Router code. React Server Components and Server Actions work seamlessly:

Next.js API SurfaceCompatibility StatusExecution Engine
App Router (app/)Full Support (v15 & v16)V8 Isolate
React Server Components (RSC)Streaming SSR SupportedV8 Isolate
Server Actions ('use server')Full SupportV8 Isolate
Route Handlers (app/api/**/route.ts)Web Request / ResponseV8 Isolate
Static Client Assets (JS/CSS/Fonts)Edge CDN CachedAnycast CDN
Native Node Modules (fs, child_process)Use Web Standards (Fetch)Web Standard APIs

Deploying to Exovon

Deploy from your local machine or continuous integration runner:

Terminal
# 1. Authenticate with your Exovon account
npx exovon login

# 2. Deploy your Vinext project (auto-detected)
npx exovon deploy

Frequently Asked Questions

What is Vinext and how is it different from standard Next.js?

Vinext is an open-source framework and Vite plugin created by Cloudflare that reimplements the Next.js API surface on top of Vite and standard Web APIs. Instead of compiling into a heavy Node.js server container via Webpack or Turbopack, Vinext builds your application into a lightweight Web Standard ES module designed for V8 Isolates. On Exovon, this delivers sub-5ms cold starts, fast local HMR, and lower memory overhead.

Do I have to rewrite my Next.js App Router code to use Vinext?

No. Vinext is built for drop-in compatibility. Your existing app/ directory, layout.tsx, page.tsx, React Server Components (RSC), Server Actions ('use server'), and Route Handlers (app/api/**/route.ts) continue working without code refactoring.

How does Exovon automatically detect and build Vinext projects?

Exovon's preflight detector analyzes your package.json dependencies and build scripts. If vinext or @vinext/core is detected, or your build script executes 'vinext build', Exovon automatically routes your project to the v8-isolate pipeline, compiling your worker bundle into an isolate without container overhead.

Can I connect to PostgreSQL or databases from Vinext on Exovon?

Yes. Because V8 Isolates run on Web Standard APIs (Fetch, WebSockets), you should use HTTP/WebSocket connection-pooled drivers such as Neon Serverless PostgreSQL (@neondatabase/serverless), Supabase, Drizzle ORM with HTTP proxy, or Prisma Accelerate.

Was this documentation page helpful?