Cloudflare Workers

→ Cloudflare Workers Documentation

What create-faster adds

A Wrangler-based deployment setup for the app. Hono already exports a Workers-compatible fetch handler (export default app), so no adapter is needed — local dev keeps running on Bun while Wrangler handles preview and deploy.

Files added:

wrangler.jsonc          # Worker config: name, main, compatibility_date, nodejs_compat

wrangler.jsonc

{
  "$schema": "node_modules/wrangler/config-schema.json",
  "name": "my-api",
  "main": "src/index.ts",
  "compatibility_date": "2026-06-12",
  "compatibility_flags": ["nodejs_compat"]
}

The Worker name is the app name in turborepo mode and the project name in single mode.

Scripts:

• deploy - Deploy the Worker (wrangler deploy)
• preview - Run the Worker locally on the Workers runtime (wrangler dev)
• cf-typegen - Generate binding types (wrangler types --env-interface CloudflareEnv cloudflare-env.d.ts)

Modified files:

• .gitignore - Ignores .wrangler/ (local state) and cloudflare-env.d.ts (generated types)

Local secrets:

Wrangler 4.x reads local secrets and variables from .env (already gitignored). Put your local values there and run wrangler dev. Production secrets are managed with wrangler secret put <KEY>. We standardize on .env rather than .dev.vars because Wrangler ignores .env whenever a .dev.vars file is present, which would silently shadow it.

Turborepo mode: wrangler.jsonc is placed in apps/<name>/, and the Worker is named after the app. Run the scripts from the app directory.

Integration notes: Cloudflare Workers and AWS Lambda are mutually exclusive Deploy libraries — an app can only deploy to one platform.