wrangler
Made by JeffDeploy and manage Cloudflare Workers, Pages, R2, D1, KV. Use when working with wrangler, Cloudflare Workers, or edge deployments.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
2Updates, enhancements, and release notes for this skill.
Updated: wrangler, examples now reach your real Cloudflare resources
In Wrangler 4, d1 execute, r2 object and kv key commands act on local development storage unless you pass --remote. The skill's examples left it off, so they read and wrote a local copy while looking successful. Every command and config key was re-checked against Wrangler 4.120.0, and about 25 wrong commands, flags and config keys were fixed.
- d1 execute, r2 object and kv key act on local storage in Wrangler 4 unless you pass --remote; the examples now do
- About 25 wrong commands, flags and config keys fixed, including cors/lifecycle --file, domain add --domain --zone-id, and hyperdrive by ID
- --x-autoconfig does not exist; wrangler deploy --autoconfig is on by default
- Routes need zone_name or zone_id next to pattern; node_compat was removed in v4
- Invented config keys (assets.include, pages_config_version) removed
Checked against Wrangler 4.120.0: the full --help tree, the bundled config-schema.json, and the CLI source.
- Local by default.
d1 execute,r2 object put/get/deleteandkv key *default to local storage. Examples that target deployed resources now pass--remote, and a gotcha explains the default.
New: Wrangler, deploy and manage Cloudflare Workers, Pages, R2, D1, KV
Cloudflare's CLI for Workers and the rest of the edge stack. The skill is the daily reference for Wrangler 4.59+: local dev, deploy, live logs, secrets, multiple environments, D1 and R2 commands, and auto-provisioned bindings. Configuration in wrangler.jsonc (recommended) over .toml.
- Quick start: wrangler dev for local, wrangler deploy for production, wrangler tail for live logs
- Auto-provisioning bindings (v4.57+): wrangler deploy creates KV, R2, and D1 resources when their IDs are missing from wrangler.jsonc. Useful for first deploys
- Environments: define staging and production under env in wrangler.jsonc, then wrangler deploy --env staging or --env production. CLOUDFLARE_API_TOKEN authenticates CI/CD and CLOUDFLARE_ACCOUNT_ID overrides the account
- Secrets workflow: wrangler secret put NAME (prompted or piped), wrangler secret list, wrangler secret delete NAME. Secrets never go in the config file
- Gotchas: keep_vars: true stops deploys from overwriting dashboard edits, wrangler types needs a re-run after config changes, and compatibility_date should be bumped yearly