wrangler@4.114.0

Minor Changes

• #14633 3203b5d Thanks @nickpatt! - Add local-dev observability

  wrangler dev and the Vite plugin now capture a trace for every local Worker invocation - spans, logs, and console.* output, including requests that cross worker or Durable Object boundaries.

  You can explore this data two ways:

  • A new Observability tab in the Local Explorer, with a Traces view (recent invocations, an inline timeline waterfall, and filters) and an Events view.
  • A read-only SQL endpoint at /cdn-cgi/explorer/api/local/observability/query, discoverable via the Local Explorer's OpenAPI document, so coding agents and tools can query the same spans and logs tables.

  While this is in testing it's off by default; set X_LOCAL_OBSERVABILITY=true to turn it on. It will be on by default in the public release.

Patch Changes

• #14373 246ce92 Thanks @Jacroney! - Improve the D1 database-limit error message

  When creating a D1 database fails because the account has hit its database limit, the error now points to the relevant next steps — upgrading on the Workers Free plan or requesting a higher limit on a paid plan — alongside the existing commands to list and delete databases. Previously it only suggested deleting unused databases. This applies both to wrangler d1 create and to the D1 database that is created during resource provisioning on deploy.

• #14796 c38a2c3 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @cloudflare/workers-types	^5.20260721.1	^5.20260722.1
  workerd	1.20260721.1	1.20260722.1

• #14788 8416b33 Thanks @chinesepowered! - Fix grammar in the container image-too-large error

  The error thrown when a container image exceeds the available disk size ended with "Your need more disk for this image." It now reads "You need more disk for this image."

• #14809 4683ff8 Thanks @jamesopstad! - Ignore the removed legacy_env field when reading a redirected configuration

  Older versions of tools such as the Vite plugin can generate a redirected configuration (.wrangler/deploy/config.json) that still includes the removed legacy_env field. Since these files are tool-generated, users could not easily remove the field themselves, and Wrangler would error out. Wrangler now silently strips legacy_env from redirected configurations. User-authored configurations still report an error so that the field can be removed.

• #14593 02232f3 Thanks @spk-ai! - Fix dev proxy silently hanging or returning a misleading 503 on network errors for non-root-path requests

  During wrangler dev, a transient network error on any request path other than / could be misclassified as the worker being reloaded, even when it wasn't: GET/HEAD requests would silently hang (with nothing logged) until the client timed out, and other methods would receive a misleading Your worker restarted mid-request 503. Such errors are now reported and surfaced immediately when the worker has not actually changed.

• #14797 f8a8c2c Thanks @roerohan! - Explain how to provision Flagship bindings if app_id missing in remote development

  Wrangler now reports that a Flagship binding without an app_id must first be created with wrangler flagship apps create.

• Updated dependencies [c38a2c3, c079ba3, 95b026e, c4bacec, 3203b5d]:

  • miniflare@4.20260722.0

miniflare@4.20260722.0

Minor Changes

• #14633 3203b5d Thanks @nickpatt! - Add local-dev observability

  wrangler dev and the Vite plugin now capture a trace for every local Worker invocation - spans, logs, and console.* output, including requests that cross worker or Durable Object boundaries.

  You can explore this data two ways:

  • A new Observability tab in the Local Explorer, with a Traces view (recent invocations, an inline timeline waterfall, and filters) and an Events view.
  • A read-only SQL endpoint at /cdn-cgi/explorer/api/local/observability/query, discoverable via the Local Explorer's OpenAPI document, so coding agents and tools can query the same spans and logs tables.

  While this is in testing it's off by default; set X_LOCAL_OBSERVABILITY=true to turn it on. It will be on by default in the public release.

Patch Changes

• #14796 c38a2c3 Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @cloudflare/workers-types	^5.20260721.1	^5.20260722.1
  workerd	1.20260721.1	1.20260722.1

• #14772 c079ba3 Thanks @chinesepowered! - Fix incorrect byte limit reported in the local Queues batch-size error

  When a queue batch exceeded the maximum batch byte size in local dev, the thrown PayloadTooLargeError hardcoded the limit as 256000, even though the value actually enforced is 288000 bytes ((256 + 32) * 1000). The message now interpolates the real limit, consistent with the other Queue limit errors in the same file.

• #14493 95b026e Thanks @petebacondarwin! - Update sharp to 0.35.2

  sharp 0.35 removes its install lifecycle script, so package managers that block dependency build scripts by default (such as pnpm 11+) no longer require an explicit build approval for it when installing miniflare/wrangler. The local Images binding keeps using the same prebuilt sharp binaries, so image transforms in local dev are unaffected.

  This release also reworked sharp's FormatEnum types: libvips reports AVIF inputs under the heif container. The local Images binding /info endpoint and the cf.image transform path now correctly report AVIF as image/avif instead of treating it as an unsupported/unknown type.

• #14792 c4bacec Thanks @matthewp! - Recover local development after the Workers runtime crashes

  Previously, an unexpected workerd crash left Miniflare running but unable to serve subsequent requests. Miniflare now restarts workerd after post-startup crashes, while continuing to surface startup crashes as fatal errors.

  The Cloudflare Vite plugin also restarts the Vite development server after workerd recovers so its environments, hot channels, and module runners are recreated.

create-cloudflare@2.70.14

Patch Changes

• #14505 65b0ccf Thanks @petebacondarwin! - Stop pre-approving sharp's build script in generated projects

  miniflare 0.35+ ships sharp 0.35, which no longer has an install lifecycle script, so generated pnpm-workspace.yaml files no longer pre-approve sharp under allowBuilds. esbuild and workerd are still pre-approved because they retain their install/postinstall scripts.

• #14761 c64cad3 Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  nuxi	3.36.1	3.37.0

• #14789 67f55b7 Thanks @dependabot! - Update dependencies of "create-cloudflare"

  The following dependency versions have been updated:

  Dependency	From	To
  create-vike	0.0.662	0.0.664

• #14613 620227d Thanks @lucasmzz! - Fix Cloudflare bindings being unavailable during nuxt dev in pnpm projects created from the Nuxt template

  The Nuxt (Workers) template explicitly installs h3 when using pnpm, so that the H3EventContext type augmentation in env.d.ts can resolve the h3 module under pnpm's isolated node_modules layout. Since h3's latest npm dist-tag moved to the 2.x release candidates, this installed h3@2.0.1-rc.x alongside the h3@1.x that Nuxt/Nitro run on. Nitro's auto-import layer then resolved getRequestURL from h3 v2, which throws when called with an h3 v1 event inside the nitro-cloudflare-dev request hook. Nitro swallows request-hook errors, so the hook silently failed before assigning event.context.cloudflare, and any server route accessing bindings crashed with "Cannot read properties of undefined (reading 'env')".

  The template now installs h3@^1, matching the h3 major that nitropack depends on.

• #14769 d059704 Thanks @edmundhung! - Stop adding a custom React Router server entry file to new projects

  React Router 8.2 now provides a Web Streams-compatible default server entry for non-Node runtimes. Newly generated Cloudflare projects use that default and only need app/entry.server.tsx for custom server rendering.

@cloudflare/workers-auth@0.5.2

Patch Changes

• #14781 fe3ae91 Thanks @edmundhung! - Make auth profile guidance CLI agnostic

  Remove Wrangler-specific wording from shared profile errors and add cf auth create to cf's auth descriptor.

@cloudflare/vitest-pool-workers@0.18.8

Patch Changes

• #14793 7b3fea6 Thanks @trafgals! - Prevent worker disposal errors from failing otherwise successful test runs

  Errors raised while disposing test Workers are now logged for diagnostics rather than overriding the test result. Set NODE_DEBUG=vitest-pool-workers to view these errors.

• Updated dependencies [246ce92, c38a2c3, 8416b33, c079ba3, 4683ff8, 95b026e, 02232f3, c4bacec, f8a8c2c, 3203b5d]:

  • wrangler@4.114.0
  • miniflare@4.20260722.0

@cloudflare/vite-plugin@1.47.0

Minor Changes

• #14633 3203b5d Thanks @nickpatt! - Add local-dev observability

  wrangler dev and the Vite plugin now capture a trace for every local Worker invocation - spans, logs, and console.* output, including requests that cross worker or Durable Object boundaries.

  You can explore this data two ways:

  • A new Observability tab in the Local Explorer, with a Traces view (recent invocations, an inline timeline waterfall, and filters) and an Events view.
  • A read-only SQL endpoint at /cdn-cgi/explorer/api/local/observability/query, discoverable via the Local Explorer's OpenAPI document, so coding agents and tools can query the same spans and logs tables.

  While this is in testing it's off by default; set X_LOCAL_OBSERVABILITY=true to turn it on. It will be on by default in the public release.

Patch Changes

• #14792 c4bacec Thanks @matthewp! - Recover local development after the Workers runtime crashes

  Previously, an unexpected workerd crash left Miniflare running but unable to serve subsequent requests. Miniflare now restarts workerd after post-startup crashes, while continuing to surface startup crashes as fatal errors.

  The Cloudflare Vite plugin also restarts the Vite development server after workerd recovers so its environments, hot channels, and module runners are recreated.

• Updated dependencies [246ce92, c38a2c3, 8416b33, c079ba3, 4683ff8, 95b026e, 02232f3, c4bacec, f8a8c2c, 3203b5d]:

  • wrangler@4.114.0
  • miniflare@4.20260722.0

@cloudflare/runtime-types@0.0.5

Patch Changes

• Updated dependencies [c38a2c3, c079ba3, 95b026e, c4bacec, 3203b5d]:
  • miniflare@4.20260722.0

@cloudflare/remote-bindings@0.0.2

Patch Changes

• Updated dependencies [fe3ae91, 246ce92, c38a2c3, c079ba3, 95b026e, c4bacec, 3203b5d]:
  • @cloudflare/workers-auth@0.5.2
  • @cloudflare/deploy-helpers@0.6.1
  • miniflare@4.20260722.0

@cloudflare/pages-shared@0.13.160

Patch Changes

• Updated dependencies [c38a2c3, c079ba3, 95b026e, c4bacec, 3203b5d]:
  • miniflare@4.20260722.0

@cloudflare/deploy-helpers@0.6.1

Patch Changes

• #14373 246ce92 Thanks @Jacroney! - Improve the D1 database-limit error message

  When creating a D1 database fails because the account has hit its database limit, the error now points to the relevant next steps — upgrading on the Workers Free plan or requesting a higher limit on a paid plan — alongside the existing commands to list and delete databases. Previously it only suggested deleting unused databases. This applies both to wrangler d1 create and to the D1 database that is created during resource provisioning on deploy.

• Updated dependencies [c38a2c3, c079ba3, 95b026e, c4bacec, 3203b5d]:

  • miniflare@4.20260722.0