What problem does it solve?
Keeps Wrangler CLI usage, configuration, and deployment practices current to avoid runtime errors, binding mismatches, and insecure secret handling when developing and operating Cloudflare Workers.
Core Features & Use Cases
- Up-to-date CLI guidance: Prefer retrieval from Cloudflare docs for the latest flags, subcommands, and config schema to avoid using stale pre-trained knowledge.
- Configuration best practices: Use wrangler.jsonc, maintain a recent compatibility_date, and generate TypeScript types after config changes to prevent binding and type mismatches.
- Local and remote workflows: Run local development with simulated bindings or enable remote bindings for integration testing; manage KV, R2, D1, Durable Objects, Workers AI, Vectorize, Hyperdrive, Containers, Queues, Workflows, Pipelines, Pages, and Secrets Store.
- Operational tooling: Tail logs, profile startup, manage versions and rollbacks, handle migrations and secrets securely, and integrate wrangler types into CI for validation.
- Use Case: Prepare a production deployment by defining env.staging and env.production, setting remote bindings for AI and Vectorize as needed, running types generation in CI, and performing a dry-run deploy before production rollout.
Quick Start
Initialize a new Cloudflare Worker project, set a recent compatibility_date in wrangler.jsonc, add required bindings (for example AI and R2), run wrangler types to generate types, and then deploy to staging for verification.