cloudflare/workers-sdk wrangler@4.151.3

on GitHub

Patch Changes

• #15611 4508172 Thanks @taylorlee! - Allow wrangler dev to start module Workers without a default export

  Previously, wrangler dev failed to start module Workers that exported only named entrypoints, such as RPC services, unless an unused default export was added. These Workers now start normally in local development without that workaround.

• #16370 61fc739 Thanks @WalshyDev! - Fetch the remote config diff from the configured compliance region

  When a Worker was last deployed from the dashboard, wrangler deploy and wrangler versions upload download its remote configuration to compare with the local one. These requests ignored the compliance_region field in the Wrangler configuration file and only honoured the CLOUDFLARE_COMPLIANCE_REGION environment variable. A FedRAMP High Worker configured through the config file would send them to api.cloudflare.com instead of api.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy.

• #15846 a88cac4 Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun

  Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.

• #16359 262021d Thanks @tw4! - Stop --strict deploys and version uploads from aborting when the API omits optional binding fields

  Previously, wrangler deploy --strict and wrangler versions upload --strict could report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker.

• Updated dependencies [3464abc]:

  • miniflare@5.20261019.1-beta