v4.20240405.0

Compare Source

v4.20240404.0

Compare Source

v4.20240403.0

Compare Source

v4.20240402.0

Compare Source

v7.5.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-floating-promises] handle TaggedTemplateExpression

• eslint-plugin: [no-unnecessary-type-assertion] handle exactOptionalPropertyTypes compiler option

❤️ Thank You

• Brad Zacher
• Kim Sang Du
• Mark de Dios
• Naru
• YeonJuan

You can read about our versioning strategy and releases on our website.

v7.5.0

Compare Source

🩹 Fixes

• parser: disallow errorOnTypeScriptSyntacticAndSemanticIssues

❤️ Thank You

• Brad Zacher
• Kim Sang Du
• Mark de Dios
• Naru
• YeonJuan

You can read about our versioning strategy and releases on our website.

v9.0.0

Compare Source

v3.20240404.0

Compare Source

Patch Changes

• #​5520 9f15ce1 Thanks @​dependabot! - chore: update dependencies of "miniflare" package

  The following dependency versions have been updated:

  Dependency	From	To
  workerd	1.20240403.0	1.20240404.0
  @​cloudflare/workers-types	^4.20240329.0	^4.20240404.0

v3.20240403.0

Compare Source

Minor Changes

• #​5215 cd03d1d Thanks @​GregBrimble! - feature: customisable unsafe direct sockets entrypoints

  Previously, Miniflare provided experimental unsafeDirectHost and unsafeDirectPort options for starting an HTTP server that pointed directly to a specific Worker. This change replaces these options with a single unsafeDirectSockets option that accepts an array of socket objects of the form { host?: string, port?: number, entrypoint?: string, proxy?: boolean }. host defaults to 127.0.0.1, port defaults to 0, entrypoint defaults to default, and proxy defaults to false. This allows you to start HTTP servers for specific entrypoints of specific Workers. proxy controls the Style of the socket.

  Note these sockets set the capnpConnectHost workerd option to "miniflare-unsafe-internal-capnp-connect". external serviceBindings will set their capnpConnectHost option to the same value allowing RPC over multiple Miniflare instances. Refer to https://github.com/cloudflare/workerd/pull/1757 for more information.

• #​5215 cd03d1d Thanks @​GregBrimble! - feature: support named entrypoints for serviceBindings

  This change allows service bindings to bind to a named export of another Worker using designators of the form { name: string | typeof kCurrentWorker, entrypoint?: string }. Previously, you could only bind to the default entrypoint. With this change, you can bind to any exported entrypoint.

  import { kCurrentWorker, Miniflare } from "miniflare";
  
  const mf = new Miniflare({
  	workers: [
  		{
  			name: "a",
  			serviceBindings: {
  				A_RPC_SERVICE: { name: kCurrentWorker, entrypoint: "RpcEntrypoint" },
  				A_NAMED_SERVICE: { name: "a", entrypoint: "namedEntrypoint" },
  				B_NAMED_SERVICE: { name: "b", entrypoint: "anotherNamedEntrypoint" },
  			},
  			compatibilityFlags: ["rpc"],
  			modules: true,
  			script: `
  			import { WorkerEntrypoint } from "cloudflare:workers";
  
  			export class RpcEntrypoint extends WorkerEntrypoint {
  				ping() { return "a:rpc:pong"; }
  			}
  
  			export const namedEntrypoint = {
  				fetch(request, env, ctx) { return new Response("a:named:pong"); }
  			};
  
  			...
  			`,
  		},
  		{
  			name: "b",
  			modules: true,
  			script: `
  			export const anotherNamedEntrypoint = {
  				fetch(request, env, ctx) { return new Response("b:named:pong"); }
  			};
  			`,
  		},
  	],
  });

Patch Changes

• #​5499 6c3be5b Thanks @​GregBrimble! - chore: Bump workerd@1.20240403.0

• #​5215 cd03d1d Thanks @​GregBrimble! - fix: allow scripts without scriptPaths to import built-in modules

  Previously, if a string script option was specified with modules: true but without a corresponding scriptPath, all imports were forbidden. This change relaxes that restriction to allow imports of built-in node:*, cloudflare:* and workerd:* modules without a scriptPath.

v3.20240329.1

Compare Source

Patch Changes

• #​5491 940ad89 Thanks @​dario-piotrowicz! - fix: make sure the magic proxy can handle multiple parallel r2 stream reads

  Currently trying to read multiple R2 streams in parallel (via Promise.all for example) leads to deadlock which prevents any of the target streams from being read. This is caused by the underlying implementation only allowing a single HTTP connection to the Workers runtime at a time. This change fixes the issue by allowing multiple parallel HTTP connections.

v5.4.4: TypeScript 5.4.4

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript 5.4.0 (Beta).
• fixed issues query for Typescript 5.4.1 (RC).
• fixed issues query for Typescript 5.4.2 (Stable).
• fixed issues query for Typescript 5.4.3 (Stable).
• fixed issues query for Typescript 5.4.4 (Stable).

Downloads are available on:

• NuGet package

v5.2.8

Compare Source

• fix: csp nonce injection when no closing tag (#​16281) (#​16282) (3c85c6b), closes #​16281 #​16282
• fix: do not access document in /@​vite/client when not defined (#​16318) (646319c), closes #​16318
• fix: fix sourcemap when using object as define value (#​15805) (445c4f2), closes #​15805
• fix(css): unknown file error happened with lightningcss (#​16306) (01af308), closes #​16306
• fix(hmr): multiple updates happened when invalidate is called while multiple tabs open (#​16307) (21cc10b), closes #​16307
• fix(scanner): duplicate modules for same id if glob is used in html-like types (#​16305) (eca68fa), closes #​16305
• chore(deps): update all non-major dependencies (#​16325) (a78e265), closes #​16325
• refactor: use types from sass instead of @​types/sass (#​16340) (4581e83), closes #​16340

v3.48.0

Compare Source

Minor Changes

• #​5429 c5561b7 Thanks @​ocsfrank! - R2 will introduce storage classes soon. Wrangler allows you to interact with storage classes once it is
  enabled on your account.

  Wrangler supports an -s flag that allows the user to specify a storage class when creating a bucket,
  changing the default storage class of a bucket, and uploading an object.

  wrangler r2 bucket create ia-bucket -s InfrequentAccess
  wrangler r2 bucket update storage-class my-bucket -s InfrequentAccess
  wrangler r2 object put bucket/ia-object -s InfrequentAccess --file foo

Patch Changes

• #​5531 887150a Thanks @​penalosa! - fix: Write wrangler pages functions build-env to file rather than stdout

• #​5526 bafbd67 Thanks @​rozenmd! - fix: teach wrangler d1 create about Australia

v3.47.1

Compare Source

Patch Changes

• Updated dependencies [9f15ce1]:
  • miniflare@3.20240404.0

v3.47.0

Compare Source

Minor Changes

• #​5506 7734f80 Thanks @​penalosa! - feat: Add interactive prompt to wrangler pages download config if an existing wrangler.toml file exists

v3.46.0

Compare Source

Minor Changes

• #​5282 b7ddde1 Thanks @​maxwellpeterson! - feature: Add source map support for Workers

  Adds the source_maps boolean config option. When enabled, source maps included in the build output are uploaded alongside the built code modules. Uploaded source maps can then be used to remap stack traces emitted by the Workers runtime.

• #​5215 cd03d1d Thanks @​GregBrimble! - feature: support named entrypoints in service bindings

  This change allows service bindings to bind to a named export of another Worker. As an example, consider the following Worker named bound:

  import { WorkerEntrypoint } from "cloudflare:workers";
  
  export class EntrypointA extends WorkerEntrypoint {
  	fetch(request) {
  		return new Response("Hello from entrypoint A!");
  	}
  }
  
  export const entrypointB: ExportedHandler = {
  	fetch(request, env, ctx) {
  		return new Response("Hello from entrypoint B!");
  	}
  };
  
  export default <ExportedHandler>{
  	fetch(request, env, ctx) {
  		return new Response("Hello from the default entrypoint!");
  	}
  };

  Up until now, you could only bind to the default entrypoint. With this change, you can bind to EntrypointA or entrypointB too using the new entrypoint option:

  [[services]]
  binding = "SERVICE"
  service = "bound"
  entrypoint = "EntrypointA"

  To bind to named entrypoints with wrangler pages dev, use the # character:

  $ wrangler pages dev --service=SERVICE=bound#EntrypointA

Patch Changes

• #​5215 cd03d1d Thanks @​GregBrimble! - fix: ensure request url and cf properties preserved across service bindings

  Previously, Wrangler could rewrite url and cf properties when sending requests via service bindings or Durable Object stubs. To match production behaviour, this change ensures these properties are preserved.

• Updated dependencies [cd03d1d, 6c3be5b, cd03d1d, cd03d1d]:

  • miniflare@3.20240403.0

v3.45.0

Compare Source

Minor Changes

• #​5377 5d68744 Thanks @​CarmenPopoviciu! - feat: Add wrangler.toml support in wrangler pages deploy

  As we are adding wrangler.toml support for Pages, we want to ensure that wrangler pages deploy works with a configuration file.

• #​5471 489b9c5 Thanks @​zebp! - feature: Add version-id filter for Worker tailing to filter logs by scriptVersion in a gradual deployment

  This allows users to only get logs in a gradual deployment if you are troubleshooting issues
  specific to one deployment. Example:
  npx wrangler tail --version-id 72d3f357-4e52-47c5-8805-90be978c403f

Patch Changes

• #​5462 68faf67 Thanks @​OilyLime! - revert: Removes support for private networking Hyperdrive configs, pending more work to support the feature. Non-breaking change since the feature wasn't yet supported.

• #​5494 a232ccf Thanks @​penalosa! - fix: Swallow parsing errors when a pages config file is required.

• #​5484 e7f8dc3 Thanks @​ichernetsky-cf! - feature: support Cloudchamber deployment labels

• #​5434 bf9dca8 Thanks @​OilyLime! - bugfix: Fix passing Hyperdrive caching options to backend

• #​5403 5d6d521 Thanks @​oliy! - fix: wrangler dev --local support for ratelimits

• Updated dependencies [940ad89]:

  • miniflare@3.20240329.1

v3.44.0

Compare Source

Minor Changes

• #​5461 f69e562 Thanks @​mattdeboard! - feature: Add command for fetching R2 Event Notification configurations for a given bucket

  This allows users to see the entire event notification configuration -- i.e. every rule for every configured queue -- for a single bucket with a single request.

  This change also improves messaging of console output when creating a new bucket notification.

Patch Changes

• #​5480 0cce21f Thanks @​penalosa! - fix: Ensure url & node:url export URL (aliased to globalThis.URL) in node_compat mode

• #​5472 02a1091 Thanks @​penalosa! - fix: Expose more info from wrangler pages functions build-env

v3.43.0

Compare Source

Minor Changes

• #​5466 ef9fbba Thanks @​celso! - feature: add Workers AI finetune commands

Patch Changes

• #​5449 91a2150 Thanks @​penalosa! - fix: Improve messaging for invalid Pages wrangler.toml files