workers-best-practices

To enforce Cloudflare Workers best practices during a code review, fetch the latest documentation and types to validate wrangler config schemas, check binding references, and detect anti-patterns like floating promises and insecure secrets.

Common Cloudflare Workers anti-patterns include floating promises, improper streaming implementations, relying on global state, and handling insecure secrets, which can all be identified by validating in-code bindings against current API shapes.

You validate wrangler config and bindings by retrieving the latest Cloudflare Workers types and documentation, then verifying that your wrangler.jsonc schema and in-code binding references match the current API shapes for reproducible reviews.

Yes, code review for Cloudflare Workers requires referencing canonical docs to justify changes, ensuring that wrangler config schemas, binding references, and security patterns are checked for auditable and reproducible results.

Yes, you can check for insecure secrets by applying retrieval-driven review rules to your Wrangler configuration and code, flagging anti-patterns and ensuring your security patterns align with canonical Cloudflare documentation.