Edge

Choose a target platform and its CLI

• Why this matters: @nextrush/adapter-edge targets the Fetch API standard, not one platform's SDK — but you still need that platform's CLI to run and deploy.

npm install -g wrangler
wrangler --version

npm install -g vercel
vercel --version

Behind the scenes: the same @nextrush/adapter-edge package produces both platforms' handler shape — createCloudflareHandler returns Cloudflare's { fetch } module export, and createVercelHandler returns the plain function Vercel's Edge runtime expects.

Install NextRush and the edge adapter

• Why this matters: like Bun and Deno, the nextrush meta-package does not bundle a runtime adapter — you add @nextrush/adapter-edge alongside it.

$ pnpm add nextrush @nextrush/adapter-edge

Behind the scenes:

• createApp and createRouter still come from nextrush — runtime-independent
• Handler factories (createCloudflareHandler, createVercelHandler, createFetchHandler) come from @nextrush/adapter-edge
• Edge has no listen() at all — there is no port to listen on

Run a hello-world fetch handler

Create the handler for your platform:

import { createApp, createRouter } from 'nextrush';
import { createCloudflareHandler } from '@nextrush/adapter-edge';

const app = createApp();
const router = createRouter();

router.get('/', (ctx) => {
  ctx.json({ runtime: ctx.runtime, status: 'ok' });
});

app.route('/', router);
export default createCloudflareHandler(app);

name = "my-nextrush-worker"
main = "src/index.ts"
compatibility_date = "2025-01-01"

wrangler dev
wrangler deploy

import { createApp, createRouter } from 'nextrush';
import { createVercelHandler } from '@nextrush/adapter-edge';

const app = createApp();
const router = createRouter();

router.get('/', (ctx) => {
  ctx.json({ runtime: ctx.runtime, status: 'ok' });
});

app.route('/', router);
export const config = { runtime: 'edge' };
export default createVercelHandler(app);

vercel dev
vercel

✅Expected result — curl https://your-worker.workers.dev/ returns {"runtime": "cloudflare-workers", "status": "ok"}

Behind the scenes:

• createCloudflareHandler(app) returns { fetch }, createVercelHandler(app) returns the fetch function directly
• Both wrap the same internal request runner — lazily boots on first request, then reuses the handler
• ctx.runtime reports 'cloudflare-workers' or 'vercel-edge' depending on where the code runs

What's structurally different about edge

Your handler is deployed. Before moving on, understand what's genuinely different — and what isn't.

Same: the Context API, createApp, createRouter, route registration, and middleware all behave identically to Node. Nothing in your route handler is edge-specific.

Different: edge runtimes give you a fetch function invoked per request, not a process you start — so @nextrush/adapter-edge has no serve()/listen() at all. The application boots lazily on the first request instead of upfront. One consequence: Extension.destroy() teardown (timers, connections) is not guaranteed to run — edge platforms give you no shutdown hook.