workers-best-practices

Reviewing Cloudflare Workers code for production readiness involves checking for common anti-patterns like floating promises and unsafe global state. You must validate wrangler.jsonc configuration, ensure correct secret handling, and verify handler signatures against the latest Workers type definitions and best-practices guidance.

Common Cloudflare Workers anti-patterns to look for in code review include floating promises, unbounded buffering, unsafe global state, and incorrect error handling. You should also check for improper secret handling, insecure randomness, and missing structured logging or observability settings in request/response flows.

Validate wrangler.jsonc settings by retrieving the latest wrangler config schema and Workers type definitions. Check binding correctness, verify handler signatures, and ensure serialization boundaries are properly defined without guessing API shapes or type signatures.

Yes, the Workers review process supports TypeScript types and Web Crypto security. It emphasizes evidence-based retrieval of Workers type definitions to validate type correctness, and enforces secure randomness via Web Crypto APIs alongside correct secret handling via wrangler secret.

Your Cloudflare Worker may fail in production due to anti-patterns not caught locally, such as unbounded buffering, unsafe global state, or incorrect error handling. Validate your wrangler.jsonc configuration and ensure your code follows current production best practices and security guidance.