workers-best-practices

Review Cloudflare Workers code by validating wrangler configuration, checking bindings, and flagging anti-patterns like floating promises or unsafe crypto usage against current production best practices to reduce bugs and security risks.

Common Cloudflare Workers anti-patterns include floating promises, module-level request state, unsafe crypto usage, and misuse of platform classes. Catching these issues early prevents outages and security mistakes caused by outdated platform assumptions.

Validate wrangler configuration by checking binding usage, secrets, and compatibility dates so code and config stay aligned. This ensures your Worker follows current Cloudflare recommendations for streaming and state management.

Yes, production best practices for Cloudflare Workers include configuring observability, managing secrets securely, and setting compatibility dates. These steps ensure your Worker is production-ready and aligned with Cloudflare's latest guidance.

Check compatibility dates when writing or reviewing Cloudflare Workers to ensure Node.js compatibility and current platform behavior. Outdated compatibility dates cause bugs and security mistakes from deprecated runtime assumptions.

Floating promises and module-level request state occur when asynchronous operations are unhandled or state persists across requests. Reviewing your Worker code against current best practices flags these anti-patterns and recommends fixes.