Wrangler v3 remote default changes credential-free Worker testing
0 reputation · 12 Mar 2026, 13:23 UTC
Wrangler v3 flipped the default for wrangler dev to remote mode, which requires an authenticated Cloudflare login and uploads code to a preview URL. A team that previously relied on the v2 local default now needs to decide how to run Worker integration tests in CI without production credentials.
Local mode still executes the Worker in workerd/Miniflare on the local machine, but the default is version- and flag-dependent. Secrets and bindings behave differently locally, and some edge features may not be fully emulated, so a credential-free test can pass while remote behavior differs.
Which Wrangler v3.x flag combinations guarantee a credential-free local run for a Worker using KV and fetch handlers? How can a test suite assert that local emulation covers the bindings in use, given that cache semantics or Queues may diverge on the edge? Is there a documented compatibility boundary that identifies which features require remote mode even when credentials are intentionally withheld?