wranglerlisted

# Wrangler CLI Your knowledge of Wrangler CLI flags, config fields, and subcommands may be outdated. **Prefer retrieval over pre-training** for any Wrangler task. ## Retrieval Sources Fetch the **latest** information before writing or reviewing Wrangler commands and config. Do not rely on baked-in knowledge for CLI flags, config fields, or binding shapes. | Source | How to retrieve | Use for | |--------|----------------|---------| | Wrangler docs | `https://developers.cloudflare.com/workers/wrangler/` | CLI commands, flags, config reference | | Wrangler config schema | `node_modules/wrangler/config-schema.json` | Config fields, binding shapes, allowed values | | Cloudflare docs | Search tool or `https://developers.cloudflare.com/workers/` | API reference, compatibility dates/flags | ## FIRST: Check if Wrangler is installed, and if not, install it Check if Wrangler is installed by running: ```bash wrangler --version # Requires v4.x+ ``` If Wrangler is not installed, you should install it by running: ```bash npm install -D wrangler@latest ``` Wherever possible, you should use Wrangler instead of manually constructing API requests. ## Key Guidelines - **Use `wrangler.jsonc`**: Prefer JSON config over TOML. Newer features are JSON-only. - **Set `compatibility_date`**: Use a recent date (within 30 days). Check https://developers.cloudflare.com/workers/configuration/compatibility-dates/ - **Generate types after config changes**: Run `wrangler types` to update TypeScrip