Minor Changes

• #11500 af54c63 Thanks @dario-piotrowicz! - Add new autoconfig_summary field to the deploy output entry

  This change augments wrangler deploy output being printed to WRANGLER_OUTPUT_FILE_DIRECTORY or WRANGLER_OUTPUT_FILE_PATH to also include a new autoconfig_summary field containing the possible summary details for the autoconfig process (the field is undefined if autoconfig didn't run).

  Note: the field is experimental and could change while autoconfig is not GA

• #11477 9988cc9 Thanks @ascorbic! - Support Nuxt in autoconfig

• #11472 ce295bf Thanks @dario-piotrowicz! - Support Qwik projects in autoconfig

• #10937 9514c9a Thanks @ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

  This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:

  • region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
  • host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
  • hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource

  These fields are mutually exclusive - only one can be specified at a time.

  Example configuration:

  [placement]
  host = "example.com:8123"

• #11498 ac861f8 Thanks @penalosa! - Add React Router support in autoconfig

• #11506 79d30d4 Thanks @vicb! - Set the target JS version to ES2024

Patch Changes

• #11393 45480b1 Thanks @alsuren! - improved --help text for wrangler d1 subcommands

• #11523 94c67e8 Thanks @jamesopstad! - fix: types from @cloudflare/workers-utils not being exported correctly from Wrangler

• #11483 f550b62 Thanks @edmundhung! - stop running npm install with --legacy-peer-deps flag when setting up a project

• Updated dependencies [819e287, 56e78c8, 0aa959a]:

  • @cloudflare/[email protected]
  • [email protected]

Patch Changes

• #11515 643f9e8 Thanks @dmmulroy! - Fix light theme syntax highlighting for variables by adding missing variable scope

Patch Changes

• #11443 56e78c8 Thanks @Ltadrian! - Improve local Hyperdrive binding latency on Windows.

Minor Changes

• #11477 9988cc9 Thanks @ascorbic! - Support Nuxt in autoconfig --experimental flow

• #11472 ce295bf Thanks @dario-piotrowicz! - Support Qwik in --experimental mode

• #11485 f1b76f7 Thanks @penalosa! - Add React & Vue to C3's experimental mode

• #11442 a75352b Thanks @brillout! - add Vike framework template

• #11498 ac861f8 Thanks @penalosa! - Add React Router support in autoconfig

• #11506 79d30d4 Thanks @vicb! - Set the target JS version to ES2024

Patch Changes

• #11472 ce295bf Thanks @dario-piotrowicz! - fix: remove unnecessary step in qwik templates

  The step that modifies the src/entry.cloudflare-pages.tsx file doesn't seem to change the file in any way anymore, so it's been removed

• #11483 f550b62 Thanks @edmundhung! - stop running npm install with --legacy-peer-deps flag when setting up a project

Minor Changes

• #10937 9514c9a Thanks @ReppCodes! - Add support for "targeted" placement mode with region, host, and hostname fields

  This change adds a new mode to placement configuration. You can specify one of the following fields to target specific external resources for Worker placement:

  • region: Specify a region identifier (e.g., "aws:us-east-1") to target a region from another cloud service provider
  • host: Specify a host with (required) port (e.g., "example.com:8123") to target a TCP service
  • hostname: Specify a hostname (e.g., "example.com") to target an HTTP resource

  These fields are mutually exclusive - only one can be specified at a time.

  Example configuration:

  [placement]
  host = "example.com:8123"

Patch Changes

• Updated dependencies [af54c63, 9988cc9, ce295bf, 45480b1, 9514c9a, 94c67e8, ac861f8, 79d30d4, 56e78c8, f550b62]:
  • [email protected]
  • [email protected]

Minor Changes

• #11506 79d30d4 Thanks @vicb! - Set the target JS version to ES2024

Patch Changes

• #11466 4f15699 Thanks @ascorbic! - Throw a more helpful error message when a Worker's entry module can't be resolved

• Updated dependencies [819e287, af54c63, 9988cc9, ce295bf, 45480b1, 9514c9a, 94c67e8, ac861f8, 79d30d4, 56e78c8, 0aa959a, f550b62]:

  • @cloudflare/[email protected]
  • [email protected]
  • [email protected]

Patch Changes

• #10606 819e287 Thanks @petebacondarwin! - Use workerd node:console when it is available

  It is enabled when the enable_nodejs_console_module compatibility flag is set.
  This flag defaults to true when nodejs_compat is turned on and the date is >= 2025-09-21.

• #10621 0aa959a Thanks @petebacondarwin! - Use native node:vm module when available

  It is enabled starting on 2025-10-01 or when the enable_nodejs_vm_module compatibility flag is set.

Patch Changes

• Updated dependencies [56e78c8]:
  • [email protected]

Patch Changes

• #11504 7e80340 Thanks @dario-piotrowicz! - Fix wrangler deploy failing for new workers containing environment variables or bindings

• Updated dependencies [59534ba]:

  • [email protected]