workers-best-practices

Validate Cloudflare Workers code by checking handlers, Durable Object patterns, and error handling against current best practices to catch outdated APIs, floating promises, and broken configuration. This process ensures your code avoids memory issues and security bugs before deployment.

Common Cloudflare Workers anti-patterns include floating promises, global request state, unsafe crypto, and pass-through error handling. Checking for these risky patterns during code review prevents memory issues and security bugs in production.

Validate wrangler.jsonc configuration by verifying compatibility dates, observability settings, secrets, nodejs_compat usage, and Env bindings. Accurate wrangler schema validation confirms your handler signatures and configuration are correct for production.

Your Cloudflare Workers project needs generated type information and up-to-date Cloudflare docs to accurately verify Env bindings and handler signatures during code review. This ensures the review catches binding mistakes and outdated APIs effectively.

Cloudflare Workers code reviews fail to catch binding mistakes when lacking up-to-date Cloudflare docs and wrangler schema validation. Accurately verifying Env bindings requires current generated type information to identify outdated APIs and broken configuration.