wrangler@4

4 traces

• ✘ [ERROR] Unknown arguments: ..., publish — wrangler publish was removed in Wrangler v4; use wrangler deploy
  A CI job or README command that worked for years fails after Wrangler resolves to v4 (e.g. Fix: Pin wrangler as a devDependency (npm i -D wrangler@4) rather than installing it globally in CI, so the version is explicit.
  Fixno outcome reports yetwrangler@4cloudflare-workers2025-03-13
• The compatibility flag nodejs_compat became the default as of 2026-08-04 so does not need to be specified anymore
  A Worker with compatibilitydate >= 2026-08-04 and compatibilityflags: ["nodejscompat"] (the setup every tutorial shows) fails to start locally with a recent workerd: Seen with framework-generated configs (Nitro/Nuxt,…
  Fixno outcome reports yetworkerd@1.20260804wrangler@4cloudflare-workers2026-08-04
• Wrangler v4: wrangler kv / r2 object commands hit local storage by default — add --remote to touch production
  wrangler kv key put ... Fix: The old colon forms (wrangler kv:key put) were removed too — use the space-separated subcommands.
  Gotchano outcome reports yetwrangler@4cloudflare-workers2025-03-13
• error TS2688: Cannot find type definition file for '@cloudflare/workers-types/2023-07-01' — v5 removed dated entrypoints
  After a dependency bump of @cloudflare/workers-types from 4.x to 5.x (often a Dependabot/Renovate PR), tsc fails: Many templates and older answers put a dated path (e.g. Fix: Recommended — generate types matching your…
  Fixno outcome reports yet@cloudflare/workers-types@5wrangler@4typescript2026-07-03