workers-best-practices

Review Cloudflare Workers code for production best practices by detecting common anti-patterns like floating promises, global request state, and unsafe streaming, ensuring your codebase meets operational standards before deployment.

Configuring wrangler.jsonc correctly requires validating fields against the latest config-schema.json, ensuring binding-code consistency, and verifying that Workers types match your declared bindings to prevent type drift.

Cloudflare Workers code requires specific security practices including using Web Crypto APIs and timing-safe comparisons to prevent security footguns, ensuring your application handles sensitive data safely.

Handle ctx.waitUntil and streaming in Cloudflare Workers by applying safe promise handling patterns and avoiding global request state, ensuring your asynchronous operations execute correctly without leaking state between requests.

Cloudflare Workers code often ships with type drift and unsafe patterns because standard development flows miss production checks against the latest @cloudflare/workers-types, allowing subtle issues to pass undetected.

You can validate observability configuration and secret usage for existing Workers codebases by reviewing your operational setup against latest official sources, ensuring safe review workflow and compatibility.