cloudflare/workers-sdk wrangler@4.150.0

on GitHub

Minor Changes

• #16231 091e5ec Thanks @WalshyDev! - Upload source maps by default for wrangler deploy, wrangler versions upload and wrangler preview

  When upload_source_maps isn't set in config or via --upload-source-maps, Wrangler now generates and uploads source maps so stack traces in logs and wrangler tail point at your original source without extra setup. In this default mode, source maps that can't be resolved (for example inline data: maps or missing .map files from a custom build) are skipped rather than failing the upload. Setting upload_source_maps = true keeps the existing strict behaviour, and upload_source_maps = false (or --no-upload-source-maps for deploy and versions upload) opts out.

  wrangler build --experimental-cf-build-output is unchanged and still only includes source maps when upload_source_maps = true.

• #16128 daae435 Thanks @redsteadz! - Stop wrangler deploy, wrangler versions upload and wrangler preview in projects that build for the Cloudflare CLI (cf)

  If your project builds through cf, deploying it with Wrangler reads a different configuration, so it could update the wrong Worker or fail without explaining why. These commands now stop before uploading anything, name the .cloudflare/output directory they found, and tell you to run cf deploy instead. If that directory is just left over from an earlier build, deleting it restores the Wrangler workflow.

  Ordinary Wrangler projects are unaffected, and --dry-run still works on deploy and versions upload. This is a new guard for the experimental Build Output Specification rather than a fix, and it gives three stable commands a failure mode they did not have before, so it is a minor.

Patch Changes

• #16161 fcf625d Thanks @dario-piotrowicz! - Clarify the Worker not found error during CI deploy validation

  Wrangler now reports that the configured Worker could not be found in the account instead of incorrectly describing the failure as a name mismatch.

• #16156 18f061c Thanks @armancharan! - Ignore .wrangler writes in the dev assets watcher

  wrangler dev reloaded in a loop when assets.directory was the project root, because the assets watcher treated wrangler's own writes under .wrangler as asset changes and dropped in-flight requests. The watcher now ignores the project's .wrangler directory and dev.persist, except when that path is the assets directory.

• #16025 61e07fd Thanks @kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds

  cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.

• #16151 cafd3f9 Thanks @DevVettel! - Time out the OAuth token request instead of waiting indefinitely

  The request that exchanges an authorization code or refresh token for an access token had no timeout, so a stalled connection (for example behind an HTTP proxy) could leave wrangler login hanging silently for many minutes after the browser step had succeeded. The request now gives up after 30 seconds and reports that the Cloudflare auth server could not be reached.

• #15517 ea64ec4 Thanks @xgame92! - Preserve binding options when provisioning resources through a redirected config

  Wrangler now writes provisioned resource identifiers to both the redirected and original config files without copying other binding options between them. This prevents generated relative paths such as D1 migrations_dir from replacing user-authored paths during Vite deployments.

• #16219 d232454 Thanks @petebacondarwin! - Honor X-Forwarded-Proto for incoming development requests behind TLS-terminating proxies

  Miniflare now uses the original client protocol when constructing URLs for network requests. This also prevents Wrangler from downgrading HTTPS URLs in response headers such as Location and WWW-Authenticate when a tunnel forwards requests over HTTP. Explicit programmatic request URLs and configured upstream origins remain authoritative.

• Updated dependencies [5152bf8, 9f87de8, 9be5ec7, d232454]:

  • miniflare@5.20261006.2-beta