Minor Changes

• #9535 56dc5c4 Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

  Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

• #9810 8acaf43 Thanks @WillTaylorDev! - WC-3626 Pull branch name from WORKERS_CI_BRANCH if exists.

Patch Changes

• #9775 4309bb3 Thanks @vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory

• #9799 d11288a Thanks @penalosa! - Better messaging for account owned tokens in wrangler whoami

• Updated dependencies [56dc5c4]:

  • miniflare@4.20250617.5

Minor Changes

• #9535 56dc5c4 Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

  Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

Patch Changes

• #9824 8104705 Thanks @petebacondarwin! - Allow "plain text" images when blocking vulnerable non-image responses

• #9785 07416ba Thanks @matthewdavidrodgers! - Handle next apps hosted at a path other than the root when blocking vulnerable non-image requests

Patch Changes

• Updated dependencies [56dc5c4, 8acaf43, 4309bb3, d11288a]:
  • miniflare@4.20250617.5
  • wrangler@4.23.0

Minor Changes

• #9535 56dc5c4 Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the [d] hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring a launch.json file, running wrangler dev, and connecting via VSCode's built-in debugger.

  Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run wrangler dev (or vite dev). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.

• #9803 df04528 Thanks @penalosa! - Support Workers Analytics Engine & Rate Limiting bindings

Patch Changes

• Updated dependencies [56dc5c4, 8acaf43, 4309bb3, d11288a]:
  • miniflare@4.20250617.5
  • wrangler@4.23.0

Patch Changes

• Updated dependencies [56dc5c4]:
  • miniflare@4.20250617.5

Patch Changes

• #9533 0a5bb5a Thanks @petebacondarwin! - fix: ensure that the sourcemap-codec library has been transformed correctly to be imported in workerd during Vitest runs

  Prior to this the inline snapshot tests were failing because they use the magic-string library, which in turn relies upon the sourcemap-codec library.

  This resulted in errors that look like:

  Error running worker: SyntaxError: The requested module '@jridgewell/sourcemap-codec' does not provide an export named 'encode'
  

Minor Changes

• #9773 45e97e8 Thanks @jamesopstad! - Vite 7 is now supported and included as a peer dependency. We continue to also support Vite 6.

• #9753 67130b3 Thanks @jamesopstad! - Allow optimizeDeps.exclude to be specified for Worker environments. This enables other plugins to exclude dependencies from optimization that require access to virtual modules. Note that excluded dependencies must be ESM.

Minor Changes

• #7871 f2a8d4a Thanks @dario-piotrowicz! - add support for assets bindings to getPlatformProxy

  this change makes sure that that getPlatformProxy, when the input configuration
  file contains an assets field, correctly returns the appropriate asset binding proxy

  example:

  // wrangler.jsonc
  {
  	"name": "my-worker",
  	"assets": {
  		"directory": "./public/",
  		"binding": "ASSETS",
  	},
  }

  import { getPlatformProxy } from "wrangler";
  
  const { env, dispose } = await getPlatformProxy();
  
  const text = await (await env.ASSETS.fetch("http://0.0.0.0/file.txt")).text();
  console.log(text); // logs the content of file.txt
  
  await dispose();

Patch Changes

• #9717 d2f2f72 Thanks @nikitassharma! - Containers should default to a "dev" instance type when no instance type is specified in the wrangler config

• #9620 1b967ea Thanks @gpanders! - Simplify containers images list output format

• #9684 94a340e Thanks @WillTaylorDev! - Select only successfully deployed deployments when tailing.

Patch Changes

• #9742 9b85137 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-vue	3.16.4	3.17.0

• #9743 8c71de1 Thanks @dependabot! - chore: update dependencies of "create-cloudflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  create-vite	6.5.0	7.0.0