cloudflare/workers-sdk wrangler@4.161.0

on GitHub

Minor Changes

• #16840 8b2a363 Thanks @jamesopstad! - Write source maps in Build Output with sources relative to each source map file

  This changes the experimental Build Output that wrangler build --experimental-cf-build-output and cf-wrangler build write. Their source maps were prepared as if for upload, with sources relative to the project root. For Workers that Wrangler does not bundle, leading ../ segments were also removed, which lost the location of some files. They now point from each source map's location in bundle/ to the original files, like the source maps the Vite plugin writes.

Patch Changes

• #16833 5f539b5 Thanks @jamesopstad! - Name cf commands and cloudflare.config.ts settings in remote bindings errors from cf-wrangler

  When cf runs development through the cf-wrangler delegate and remote bindings cannot be authenticated, the error now tells you to run cf auth whoami, cf auth logout and cf auth login instead of the Wrangler commands, and the Cloudflare Access hint names cf. The Flagship error for a binding whose app has not been created now names the binding's id setting instead of app_id, and suggests cf flagship apps create. wrangler dev still names Wrangler's commands and settings.

• #16527 dc47e6d Thanks @petebacondarwin! - Normalize relative redirect pathnames consistently across Pages and Workers assets

  Relative _redirects targets now use shared pathname normalization after placeholder replacement, keeping repeated separators within the site's path. Explicit external targets (including scheme-less URLs such as //example.com/path), query values and fragments retain their contents.

• #16559 575d136 Thanks @edmundhung! - Update @netlify/build-info to 11.3.1

• #16838 3626ee8 Thanks @jamesopstad! - Keep the remote bindings session when you remove the last remote binding

  When you removed the last remote binding while wrangler dev was running, Wrangler restarted the remote bindings session with credentials that ignored --profile and the account_id in your Wrangler config. So it could use a different account or ask you to choose one. Wrangler now keeps the existing session, and starts a new one with your current credentials when you add a remote binding again.

• Updated dependencies [dc47e6d]:

  • miniflare@5.20261110.2-beta