workers-best-practices

To review Cloudflare Workers code for security and production issues, validate your fetch handlers and wrangler configuration against up-to-date best practices to prevent floating promises, unsafe secret handling, and incorrect ctx or env usage.

Common Cloudflare Workers anti-patterns include floating promises, module-level request state, unsafe token generation, insecure randomness, and incorrect binding access patterns. Validating compatibility_date and observability settings helps avoid these production failures.

Validate wrangler configuration by checking compatibility dates, observability settings, secrets usage, and binding-code consistency against the wrangler config schema and generated types to ensure safe Cloudflare Workers deployment.

Cloudflare Workers require specific configuration for streaming and background execution to prevent production failures. You must validate compatibility_date, bindings, and async execution patterns against current best practices for safe operations.

Incorrect ctx or env usage in Cloudflare Workers often stems from improper binding access patterns or module-level request state. Reviewing your fetch handler against type schema sources and best practices resolves these configuration mismatches.