Bindings

A binding is a value Cloudflare injects onto env when the Worker runs. better-router exposes that object on the request:

import { getEnv } from "better-router";
import type { LoaderArgs } from "better-router";

export async function loader({ c }: LoaderArgs) {
  const env = getEnv();
  // same object as c.env
  return { url: env.APP_URL };
}

Declare bindings in wrangler.jsonc. Type them by augmenting AppBindings.

Binding map

Binding	Cloudflare product	Typical `env` name
D1	SQLite database	`DB`
KV	Key-value store	`KV`
R2	Object storage	`BUCKET`
Queue producer	Queues	`EMAILS`
Queue consumer	Queues	Worker `queue` handler
Email (inbound)	Email Routing	Worker `email` handler
Cron	Cron Triggers	Worker `scheduled` handler
Assets	Static Assets	`assets.directory`
Vars	Plain env vars	`c.env.APP_URL`
Secrets	Encrypted env vars	`c.env.STRIPE_SECRET`

better-router does not wrap these products. Use the Cloudflare APIs (or your own clients) against getEnv().

D1

wrangler.jsonc

{
  "d1_databases": [
    {
      "binding": "DB",
      "database_name": "app",
      "database_id": "<id>"
    }
  ]
}

export async function loader() {
  const { DB } = getEnv() as { DB: D1Database };
  const { results } = await DB.prepare("select id, name from users").all();
  return { users: results };
}

Create the database with npx wrangler d1 create app.

KV

wrangler.jsonc

{
  "kv_namespaces": [
    {
      "binding": "KV",
      "id": "<namespace-id>"
    }
  ]
}

const kv = getEnv().KV as KVNamespace;
await kv.put("feature:checkout", JSON.stringify({ enabled: true }), { expirationTtl: 3600 });
const flag = await kv.get("feature:checkout", "json");

Create a namespace with npx wrangler kv namespace create KV.

R2

wrangler.jsonc

{
  "r2_buckets": [
    {
      "binding": "BUCKET",
      "bucket_name": "app-media"
    }
  ]
}

const bucket = getEnv().BUCKET as R2Bucket;
await bucket.put("avatars/1.png", file);
const object = await bucket.get("avatars/1.png");

Create a bucket with npx wrangler r2 bucket create app-media.

Queues

Queues have two sides:

Producer — env.EMAILS.send(body) from a request or cron
Consumer — the Worker queue handler in src/worker.ts

wrangler.jsonc

{
  "queues": {
    "producers": [{ "binding": "EMAILS", "queue": "emails" }],
    "consumers": [{ "queue": "emails" }]
  }
}

const emails = getEnv().EMAILS as Queue;
await emails.send({ to: "ada@example.com" });

The consumer is defineWorker({ queue }) — see Worker entrypoint.

Email (inbound)

Email Routing can deliver inbound messages to a Worker. Handle them with defineWorker({ email }).

Cron Triggers

Cron expressions live on the Worker, not in DNS.

wrangler.jsonc

{
  "triggers": {
    "crons": ["*/5 * * * *", "0 9 * * *"]
  }
}

The scheduled event’s cron string is event.cron in defineWorker({ scheduled }). Exporting a handler is not enough — Cloudflare only fires alarms listed in Wrangler.

Assets

The client build is static files. Wrangler serves them in front of the Worker so /assets/client.js does not hit Hono.

{
  "assets": { "directory": "./dist/client" }
}

Files in public/ are copied by Vite into that directory.

Vars and secrets

Plain values go in vars. Secrets go through wrangler secret put and never sit in git.

{
  "vars": {
    "APP_URL": "https://example.com"
  }
}

npx wrangler secret put STRIPE_SECRET

Read them with getEnv().STRIPE_SECRET. Locally, put secrets in .dev.vars (Wrangler) or .env (Vite). See Environment.

Type the env

src/env.d.ts

declare module "better-router" {
  interface AppBindings {
    DB: D1Database;
    KV: KVNamespace;
    BUCKET: R2Bucket;
    EMAILS: Queue;
    APP_URL: string;
    STRIPE_SECRET: string;
  }
}

Then getEnv().DB typechecks in loaders, actions, and middleware.

Example `wrangler.jsonc`

wrangler.jsonc

{
  "name": "my-app",
  "compatibility_date": "2026-09-01",
  "compatibility_flags": ["nodejs_compat"],
  "main": "./dist/server/index.js",
  "assets": { "directory": "./dist/client" },
  "vars": {
    "APP_URL": "https://example.com"
  },
  "d1_databases": [
    { "binding": "DB", "database_name": "app", "database_id": "<id>" }
  ],
  "kv_namespaces": [
    { "binding": "KV", "id": "<id>" }
  ],
  "r2_buckets": [
    { "binding": "BUCKET", "bucket_name": "app-media" }
  ],
  "queues": {
    "producers": [{ "binding": "EMAILS", "queue": "emails" }],
    "consumers": [{ "queue": "emails" }]
  },
  "triggers": {
    "crons": ["*/5 * * * *"]
  }
}

Other Cloudflare products

These are available on c.env if you bind them:

Binding	Use
Hyperdrive	Pooled Postgres/MySQL
Durable Objects	Stateful coordination; read `c.env.COUNTER` yourself
Workers AI	Inference; call `c.env.AI` yourself
Vectorize	Vector search
Workflows	Durable multi-step jobs

Add them in Wrangler and type them on AppBindings the same way. See examples/cloudflare for D1, a queue producer/consumer, and cron in one app.

Get started

Routing

Rendering

Deploy

Guides

Reference

Binding map

D1

KV

R2

Queues

Email (inbound)

Cron Triggers

Assets

Vars and secrets

Type the env

Example `wrangler.jsonc`

Other Cloudflare products

​Binding map

​D1

​KV

​R2

​Queues

​Email (inbound)

​Cron Triggers

​Assets

​Vars and secrets

​Type the env

​Example wrangler.jsonc

​Other Cloudflare products

Binding map

D1

KV

R2

Queues

Email (inbound)

Cron Triggers

Assets

Vars and secrets

Type the env

Example `wrangler.jsonc`

Other Cloudflare products