Cloudflare Workers

better-router can run anywhere that speaks fetch. Cloudflare Workers is a first-class target, not the only one. If the project contains wrangler.toml, wrangler.json, or wrangler.jsonc, the plugin sets target: "cloudflare" automatically. You can also set it yourself:

betterRouter({ target: "cloudflare" })

What gets deployed

vite build emits:

Output	Role
`dist/client`	Browser assets, SPA runtime, island hydrators
`dist/server/index.js`	Worker module with `fetch`, plus `scheduled`, `queue`, and `email`

Wrangler should point at that server file and serve the client as static assets:

wrangler.jsonc

{
  "name": "my-app",
  "compatibility_date": "2026-09-01",
  "compatibility_flags": ["nodejs_compat"],
  "main": "./dist/server/index.js",
  "assets": {
    "directory": "./dist/client"
  }
}

nodejs_compat is required for request-scoped helpers that use AsyncLocalStorage (getEnv(), getHonoContext()).

Deploy

npx vite build
npx wrangler deploy

Worker handlers

The generated module looks like this:

export default {
  fetch,       // Hono app: pages, APIs, middleware
  scheduled,   // Cron triggers from src/worker.ts
  queue,       // Queue consumers from src/worker.ts
  email,       // Inbound Email Routing from src/worker.ts
}

Handler	Cloudflare feature	App files
`fetch`	HTTP requests	`src/routes`, `src/middleware`
`scheduled`	Cron Triggers	`src/worker.ts`
`queue`	Queues consumer	`src/worker.ts`
`email`	Email Workers	`src/worker.ts`

fetch is always the Hono app unless you override it in defineWorker({ fetch }). The other three no-op until you implement them. See Bindings for D1, KV, R2, Queues, and secrets. See Worker entrypoint for defineWorker.

Local development

vite dev runs the Hono fetch handler. Cron, queue, and inbound email do not fire locally. Use wrangler dev against the production build when you need Miniflare bindings (DB, KV, BUCKET, queue producers):

npx vite build
npx wrangler dev

Put local secrets in .dev.vars, not .env, when you use Wrangler.

Example

examples/cloudflare is a Worker that uses all three:

Binding	What the example does
D1 `DB`	Stores jobs and cron heartbeats
Queue `JOBS`	Form and cron enqueue work; `defineWorker({ queue })` marks jobs done
Cron `* * * * *`	`defineWorker({ scheduled })` writes a heartbeat and enqueues a ping

pnpm --filter better-router-example-cloudflare db:migrate
pnpm --filter better-router-example-cloudflare dev:worker

Node, Bun, and Deno

The same worker module is a standard fetch listener. Cloudflare-only bindings (D1, R2, KV, Queues) exist on env in production. On Node, pass process.env as the second argument to worker.fetch — see Deployment.

Get started

Routing

Rendering

Deploy

Guides

Reference

What gets deployed

Deploy

Worker handlers

Local development

Example

Node, Bun, and Deno

​What gets deployed

​Deploy

​Worker handlers

​Local development

​Example

​Node, Bun, and Deno

What gets deployed

Deploy

Worker handlers

Local development

Example

Node, Bun, and Deno