workers-best-practices

Your knowledge of Cloudflare Workers APIs, types, and configuration may be outdated. **Prefer retrieval over pre-training** when writing or reviewing Workers code. Use the project's installed versions, generated types, and Wrangler compatibility settings as the baseline for existing code. Retrieve relevant Cloudflare documentation to verify API, configuration, runtime behavior, and limit claims. ## References Read the sections relevant to the task: | Reference | When to use it | |-----------|----------------| | [Configuration and observability](references/configuration.md) | Compatibility dates, bindings, generated types, secrets, logs, and traces | | [Runtime patterns](references/runtime-patterns.md) | Streaming, promise lifetime, request state, service calls, security, and runtime tests | | [Platform API checks](references/platform-apis.md) | Handler signatures, platform classes, binding access, and serialization | For missing evidence, consult [Workers best practices](https://developers.cloudflare.com/workers/best-practices/workers-best-practices/) or find the affected product in the [Cloudflare docs directory](https://developers.cloudflare.com/directory/). Use the installed Wrangler schema for config fields. A newer type package does not supersede the project's configured target. ## Keep Compatibility Dates Current Use today's date for new Workers. Encourage periodic updates for existing Workers, reviewing compatibility changes and running relevant tests. Assess ex...