| name | cloudflare-workers |
| description | Cloudflare Workers patterns for Worker runtime APIs, Durable Objects, KV, R2, D1, Queues, WebSockets, streaming responses, bindings, wrangler configuration, and deployment limits. Use when users mention Cloudflare Workers, Durable Objects, KV, R2, D1, Queues, wrangler, or edge runtime behavior. |
| metadata | {"author":"epicenter","version":"1.0"} |
Cloudflare Workers
Reference Repositories
- Cloudflare Docs - Workers, Durable Objects, KV, R2, D1, Queues, WebSockets, bindings, and deployment docs
- Hono - TypeScript web framework commonly used on Workers
Upstream Grounding
When Worker runtime behavior, bindings, Durable Objects, WebSockets, streaming, cache APIs, service bindings, compatibility dates, limits, or wrangler configuration affect correctness, ask DeepWiki a narrow question against cloudflare/cloudflare-docs before relying on memory. Use honojs/hono as the grounding repo when the question is about Hono on Workers.
Verify decisive details against local generated Worker types, source, or official Cloudflare docs before changing code. Skip DeepWiki for stable Web API basics and repo-local deployment patterns already visible in the code.
Request Lifecycle Rules
- Every async side effect must be awaited, returned, or passed to
c.executionCtx.waitUntil(...). Floating promises are unsafe because the isolate can stop after the response.
- Call
waitUntil as a method on c.executionCtx. Do not destructure it.
- Keep
waitUntil work bounded and best-effort. Use Queues for guaranteed or long-running work.
