npm · #4709 most downloaded on npm

wrangler

4.147.094M downloads/mocloudflare/workers-sdk ↗New releases in your daily digest, changelog included.

Command-line interface for all things Cloudflare Workers

Last release 2 days ago
02 Oct 2026
Ships on a steady schedule
a new release about every 9 days
Nearly every release is documented
notes for 60 of the last 60 stable releases
119 versions withdrawn
withdrawn after publishing
14 years old
4955 releases · first in 2012

Release timeline

4955 releases since 2012

2012201420162018

Releases

3.110.025 Feb 2025
Updated dependencies [`a9a4c33`, `6cae13a`]:
Minor Changes

#8253 6dd1e23 Thanks @CarmenPopoviciu! - Add --cwd global argument to the wrangler CLI to allow changing the current working directory before running any command.

Patch Changes

#8191 968c3d9 Thanks @vicb! - Optimize global injection in node compat mode

#8247 a9a4c33 Thanks @GregBrimble! - feat: Omits Content-Type header for files of an unknown extension in Workers Assets

Updated dependencies [a9a4c33, 6cae13a]:

miniflare@3.20250214.1
Open source →

3.109.013 Feb 2025

This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format

Minor Changes

#8120 3fb801f Thanks @sdnts! - Add a new update subcommand for Queues to allow updating Queue settings
#8120 3fb801f Thanks @sdnts! - Allow overriding message retention duration when creating Queues
#8026 542c6ea Thanks @penalosa! - Add --outfile to wrangler deploy for generating a worker bundle.

This is an advanced feature that most users won't need to use. When set, Wrangler will output your built Worker bundle in a Cloudflare specific format that captures all information needed to deploy a Worker using the Worker Upload API
#8026 542c6ea Thanks @penalosa! - Add a wrangler check startup command to generate a CPU profile of your Worker's startup phase.

This can be imported into Chrome DevTools or opened directly in VSCode to view a flamegraph of your Worker's startup phase. Additionally, when a Worker deployment fails with a startup time error Wrangler will automatically generate a CPU profile for easy investigation.

Advanced usage:
- --args: to customise the way wrangler check startup builds your Worker for analysis, provide the exact arguments you use when deploying your Worker with wrangler deploy. For instance, if you deploy your Worker with wrangler deploy --no-bundle, you should use wrangler check startup --args="--no-bundle" to profile the startup phase.
- --worker-bundle: if you don't use Wrangler to deploy your Worker, you can use this argument to provide a Worker bundle to analyse. This should be a file path to a serialised multipart upload, with the exact same format as the API expects: https://developers.cloudflare.com/api/resources/workers/subresources/scripts/methods/update/

Patch Changes

#8112 fff677e Thanks @penalosa! - When reporting errors to Sentry, Wrangler will now include the console output as additional metadata
#8120 3fb801f Thanks @sdnts! - Check bounds when overriding delivery delay when creating Queues
#7950 4db1fb5 Thanks @cmackenzie1! - Add local binding support for Worker Pipelines
#8119 1bc60d7 Thanks @penalosa! - Output correct config format from wrangler d1 create. Previously, this command would always output TOML, regardless of the config file format
#8130 1aa2a91 Thanks @emily-shen! - Include default values for wrangler types --path and --x-include-runtime in telemetry

User provided strings are still left redacted as always.
#8061 35710e5 Thanks @emily-shen! - fix: respect WRANGLER_LOG in wrangler dev

Previously, --log-level=debug was the only way to see debug logs in wrangler dev, which was unlike all other commands.
Updated dependencies [4db1fb5]:
- miniflare@3.20250204.1

Open source →

3.108.011 Feb 2025withdrawn: Regression with `wrangler secret list --format json` emitting non-JSON characters. Downgrade to 3.107.3

We currently print a worker's bindings during dev, versions upload and deploy. This just also prints something when there's no bindings found, in case

Minor Changes

#7990 b1966df Thanks @cmsparks! - Add WRANGLER_CI_OVERRIDE_NAME for Workers CI
#8028 b2dca9a Thanks @emily-shen! - feat: Also log when no bindings are found.

We currently print a worker's bindings during dev, versions upload and deploy. This just also prints something when there's no bindings found, in case you were expecting bindings.
#8037 71fd250 Thanks @WillTaylorDev! - Provides unsafe.metadata configurations when using wrangler versions secret put.

Patch Changes

#8058 1f80d69 Thanks @WillTaylorDev! - Bugfix: Modified versions secret put to inherit all known bindings, which circumvents a limitation in the API which does not return all fields for all bindings.
#7986 88514c8 Thanks @andyjessop! - docs: clarifies that local resources are "simulated locally" or "connected to remote resource", and adds console messages to help explain local dev
#8008 9d08af8 Thanks @ns476! - Add support for Images bindings (in private beta for now), with optional local support for platforms where Sharp is available.
#7769 6abe69c Thanks @cmackenzie1! - Adds the following new option for wrangler pipelines create and wrangler pipelines update commands:
```
--cors-origins           CORS origin allowlist for HTTP endpoint (use * for any origin)  [array]
```
#7290 0c0374c Thanks @emily-shen! - fix: add support for workers with assets when running multiple workers in one wrangler dev instance

https://github.com/cloudflare/workers-sdk/pull/7251 added support for running multiple Workers in one wrangler dev/miniflare session. e.g. wrangler dev -c wrangler.toml -c ../worker2/wrangler.toml, which among other things, allowed cross-service RPC to Durable Objects.

However this did not work in the same way as production when there was a Worker with assets - this PR should fix that.

#7769 6abe69c Thanks @cmackenzie1! - Rename wrangler pipelines <create|update> flags

The following parameters have been renamed:

Previous Name	New Name
access-key-id	r2-access-key-id
secret-access-key	r2-secret-access-key
transform	transform-worker
r2	r2-bucket
prefix	r2-prefix
binding	enable-worker-binding
http	enable-http
authentication	require-http-auth
filename	file-template
filepath	partition-template

#8012 c412a31 Thanks @mtlemilio! - Use fetchPagedListResult when listing Hyperdrive configs from the API

This fixes an issue where only 20 configs were being listed.
#8077 60310cd Thanks @emily-shen! - feat: add telemetry to experimental auto-provisioning
Updated dependencies [c80dbd8, 0c0374c]:
- miniflare@3.20250204.0

Open source →

3.107.030 Jan 2025withdrawn: There is a regression in Wrangler 3.107.0 in which [assets] was not being inherited from the top-level environment. Please downgrade to v3.106.0 for now.

when getPlatformProxy is called and it retrieves values from .dev.vars files, it logs twice a message like: Using vars defined in .dev.vars, the chang

Minor Changes

#7897 34f9797 Thanks @WillTaylorDev! - chore: provides run_worker_first for Worker-script-first configuration. Deprecates experimental_serve_directly.

Patch Changes

#7945 d758215 Thanks @ns476! - Add Images binding (in private beta for the time being)
#7947 f57bc4e Thanks @dario-piotrowicz! - fix: avoid getPlatformProxy logging twice that it is using vars defined in .dev.vars files

when getPlatformProxy is called and it retrieves values from .dev.vars files, it logs twice a message like: Using vars defined in .dev.vars, the changes here make sure that in such cases this log only appears once
#7889 38db4ed Thanks @emily-shen! - feat: add experimental resource auto-provisioning to versions upload
#7864 de6fa18 Thanks @dario-piotrowicz! - Update the unstable_getMiniflareWorkerOptions types to always include an env parameter.

The unstable_getMiniflareWorkerOptions types, when accepting a config object as the first argument, didn't accept a second env argument. The changes here make sure they do, since the env is still relevant for picking up variables from .dev.vars files.
#7964 bc4d6c8 Thanks @LuisDuarte1! - Fix scripts binding to a workflow in a different script overriding workflow config
Updated dependencies [cf4f47a]:
- miniflare@3.20250124.1

Open source →

3.106.028 Jan 2025

Error messages that have been audited for potential inclusion of personal information, and explicitly opted-in, are now included in Wrangler's telemet

Minor Changes

#7856 2b6f149 Thanks @emily-shen! - feat: add sanitised error messages to Wrangler telemetry

Error messages that have been audited for potential inclusion of personal information, and explicitly opted-in, are now included in Wrangler's telemetry collection. Collected error messages will not include any filepaths, user input or any other potentially private content.
#7900 bd9228e Thanks @vicb! - chore(wrangler): update unenv dependency version

unenv@2.0.0-rc.1 allows using the workerd implementation for the Node modules net, timers, and timers/promises. See unjs/unenv#396.

Patch Changes

#7904 50b13f6 Thanks @WalshyDev! - fix: validation for R2 bucket names, the regex was wrongly rejecting buckets starting with a number and the message wasn't as clear as it could be on what was going wrong.
#7895 134d61d Thanks @jahands! - Fix regression in retryOnAPIFailure preventing any requests from being retried

Also fixes a regression in pipelines that prevented 401 errors from being retried when waiting for an API token to become active.
#7879 5c02e46 Thanks @andyjessop! - Fix to not require local connection string when using Hyperdrive and wrangler dev --remote
#7860 13ab591 Thanks @vicb! - refactor(wrangler): make JSON parsing independent of Node

Switch jsonc-parser to parse json:
- JSON.parse() exception messages are not stable across Node versions
- While jsonc-parser is used, JSONC specific syntax is disabled
Updated dependencies []:
- miniflare@3.20250124.0

Open source →

3.105.022 Jan 2025

This command allows users to upload a mTLS certificate/private key or certificate-authority certificate chain.

Minor Changes

#7466 e5ebdb1 Thanks @Ltadrian! - feat: implement the wrangler cert upload command

This command allows users to upload a mTLS certificate/private key or certificate-authority certificate chain.

For uploading mTLS certificate, run:
- wrangler cert upload mtls-certificate --cert cert.pem --key key.pem --name MY_CERT
For uploading CA certificate chain, run:
- wrangler cert upload certificate-authority --ca-cert server-ca.pem --name SERVER_CA

Patch Changes

#7867 bdc7958 Thanks @penalosa! - Revert https://github.com/cloudflare/workers-sdk/pull/7816. This feature added support for the ASSETS bindings to the getPlatformProxy() API, but caused a regression when running npm run preview in newly generated Workers Assets projects.
#7868 78a9a2d Thanks @penalosa! - Revert "Hyperdrive dev remote fix". This PR includes e2e tests that were not run before merging, and are currently failing.
Updated dependencies []:
- miniflare@3.20241230.2

Open source →

3.104.022 Jan 2025withdrawn: Downgrade to 3.103.2

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

Minor Changes

#7715 26fa9e8 Thanks @penalosa! - Support service bindings from Pages projects to Workers in a single workerd instance. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler pages dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first -c flag must point to your Pages config file, and the rest should point to Workers that are bound to your Pages project.

#7816 f6cc029 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.json
{
  "name": "my-worker",
  "assets": {
    "directory": "./public/",
    "binding": "ASSETS"
  },
  "vars": {
    "MY_VAR": "my-var"
  }
}

import { getPlatformProxy } from "wrangler";

const { env, dispose } = await getPlatformProxy();

if (env.ASSETS) {
  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

#7785 cccfe51 Thanks @joshthoward! - Fix Durable Objects transfer migration validation
#7821 fcaa02c Thanks @vicb! - fix(wrangler): fix wrangler config schema defaults
#7832 97d2a1b Thanks @petebacondarwin! - Relax the messaging when Wrangler uses redirected configuration

Previously the messaging was rendered as a warning, which implied that the user had done something wrong. Now it is just a regular info message.
#7806 d7adb50 Thanks @vicb! - chore: update unenv to 2.0.0-rc.0

Pull a couple changes in node:timers
- unjs/unenv#384 fix function bindings in node:timer
- unjs/unenv#385 implement active and _unrefActive in node:timer
The unenv update also includes #unjs/unenv/381 which implements stdout, stderr and stdin of node:process with node:tty
#7828 9077a67 Thanks @edmundhung! - improve multi account error message in non-interactive mode
Updated dependencies []:
- miniflare@3.20241230.2

Open source →

3.103.016 Jan 2025withdrawn: Downgrade to 3.99.0

add a new --strict-vars option to wrangler types that developers can (by setting the flag to false) use to disable the default strict/literal types ge

Minor Changes

#5086 8faf2c0 Thanks @dario-piotrowicz! - add --strict-vars option to wrangler types

add a new --strict-vars option to wrangler types that developers can (by setting the flag to false) use to disable the default strict/literal types generation for their variables

opting out of strict variables can be useful when developers change often their vars values, even more so when multiple environments are involved

Example

With a toml containing:
```
[vars]
MY_VARIABLE = "production_value"
MY_NUMBERS = [1, 2, 3]

[env.staging.vars]
MY_VARIABLE = "staging_value"
MY_NUMBERS = [7, 8, 9]
```
the wrangler types command would generate the following interface:
```
interface Env {
        MY_VARIABLE: "production_value" | "staging_value";
        MY_NUMBERS: [1,2,3] | [7,8,9];
}
```
while wrangler types --strict-vars=false would instead generate:
```
interface Env {
        MY_VARIABLE: string;
        MY_NUMBERS: number[];
}
```
(allowing the developer to easily change their toml variables without the risk of breaking typescript types)

Patch Changes

#7720 902e3af Thanks @vicb! - chore(wrangler): use the unenv preset from @cloudflare/unenv-preset
#7760 19228e5 Thanks @vicb! - chore: update unenv dependency version
#7735 e8aaa39 Thanks @penalosa! - Unwrap the error cause when available to send to Sentry
#5086 8faf2c0 Thanks @dario-piotrowicz! - fix: widen multi-env vars types in wrangler types

Currently, the type generated for vars is a string literal consisting of the value of the variable in the top level environment. If multiple environments are specified this wrongly restricts the type, since the variable could contain any of the values from each of the environments.

For example, given a wrangler.toml containing the following:
```
[vars]
MY_VAR = "dev value"

[env.production.vars]
MY_VAR = "prod value"
```
running wrangler types would generate:
```
interface Env {
  MY_VAR: "dev value";
}
```
making typescript incorrectly assume that MY_VAR is always going to be "dev value"

after these changes, the generated interface would instead be:
```
interface Env {
  MY_VAR: "dev value" | "prod value";
}
```
#7733 dceb196 Thanks @emily-shen! - feat: pull resource names for provisioning from config if provided

Uses database_name and bucket_name for provisioning if specified. For R2, this only happens if there is not a bucket with that name already. Also respects R2 jurisdiction if provided.
Updated dependencies []:
- miniflare@3.20241230.2

Open source →

3.101.09 Jan 2025withdrawn: Downgrade to 3.99.0

Run wrangler secret bulk .dev.vars to add the env file

Minor Changes

#7534 7c8ae1c Thanks @cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines
#7674 45d1d1e Thanks @Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

Run wrangler secret bulk .dev.vars to add the env file
```
//.dev.vars
KEY=VALUE
KEY_2=VALUE
```
This will upload the secrets KEY and KEY_2 to your worker
#7442 e4716cc Thanks @petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

This new feature is designed for build tools and frameworks to provide a deploy-specific configuration, which Wrangler can use instead of user configuration when running deploy-related commands. It is not expected that developers of Workers will need to use this feature directly.

Affected commands

The commands that use this feature are:
- wrangler deploy
- wrangler dev
- wrangler versions upload
- wrangler versions deploy
- wrangler pages deploy
- wrangler pages build
- wrangler pages build-env
Config redirect file

When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:
```
{ "configPath": "../../path/to/wrangler.json" }
```
When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

Custom build tool example

A common approach that a build tool might choose to implement.
- The user writes code that uses Cloudflare Workers resources, configured via a user wrangler.toml file.
```
name = "my-worker"
main = "src/index.ts"
[[kv_namespaces]]
binding = "<BINDING_NAME1>"
id = "<NAMESPACE_ID1>"
```
  Note that this configuration points main at user code entry-point.
- The user runs a custom build, which might read the wrangler.toml to find the entry-point:
```
> my-tool build
```
- This tool generates a dist directory that contains both compiled code and a new deployment configuration file, but also a .wrangler/deploy/config.json file that redirects Wrangler to this new deployment configuration file:
```
- dist
  - index.js
	- wrangler.json
- .wrangler
  - deploy
	  - config.json
```
  The dist/wrangler.json will contain:
```
{
  "name": "my-worker",
  "main": "./index.js",
  "kv_namespaces": [
    { "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
  ]
}
```
  And the .wrangler/deploy/config.json will contain:
```
{
  "configPath": "../../dist/wrangler.json"
}
```
#7685 9d2740a Thanks @vicb! - allow overriding the unenv preset.

By default wrangler uses the bundled unenv preset.

Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset. Those paths are used when resolving the unenv module identifiers to absolute paths. This can be used to test a development version.
#7694 f3c2f69 Thanks @joshthoward! - Default wrangler d1 export to --local rather than failing

Patch Changes

#7456 ff4e77e Thanks @andyjessop! - chore: removes --experimental-versions flag, as versions is now GA.
#7712 6439347 Thanks @penalosa! - Remove CF-Connecting-IP for requests to the edge preview
#7703 e771fe9 Thanks @petebacondarwin! - include the top level Worker name in the parsed config structure
#7576 773bda8 Thanks @cmackenzie1! - Remove defaults for batch-max-* pipeline parameters and define value ranges
Updated dependencies [2c76887, 78bdec5]:
- miniflare@3.20241230.1

Open source →

3.100.07 Jan 2025withdrawn: Downgrade to 3.99.0

We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data poin

Minor Changes

#7604 6c2f173 Thanks @CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

#7581 cac7fa6 Thanks @vicb! - chore(wrangler): update unenv dependency version

unenv now uses the workerd implementation on node:dns See the unjs/unenv#376
#7625 d8fb032 Thanks @vicb! - feat(wrangler): use unenv builtin dependency resolution

Moving away from require.resolve() to handle unenv aliased packages. Using the unenv builtin resolution will allow us to drop the .cjs file from the preset and to override the base path so that we can test the dev version of the preset.
#7533 755a27c Thanks @danielgek! - Add warning about the browser rendering not available on local
#7614 8abb43f Thanks @vicb! - chore(wrangler): update unenv dependency version

The updated unenv contains a fix for the module resolution, see https://github.com/unjs/unenv/pull/378. That bug prevented us from using unenv module resolution, see https://github.com/cloudflare/workers-sdk/pull/7583.
Updated dependencies [b4e0af1]:
- miniflare@3.20241230.0

Open source →

3.99.019 Dec 2024

Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper

Minor Changes

#7425 8757579 Thanks @CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:
1. check for asset files changes
2. upload the changed assets, if any
This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.
#7537 086a6b8 Thanks @WillTaylorDev! - Provide validation around assets.experimental_serve_directly
#7568 2bbcb93 Thanks @WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

#7521 48e7e10 Thanks @emily-shen! - feat: add experimental_patchConfig()

experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.
Updated dependencies [1488e11, 7216835]:
- miniflare@3.20241218.0

Open source →

3.98.019 Dec 2024

Adds a Wrangler API to find and read a config file

Minor Changes

#7476 5124b5d Thanks @WalshyDev! - feat: allow routing to Workers with Assets on any HTTP route, not just the root. For example, example.com/blog/* can now be used to serve assets. These assets will be served as though the assets directly were mounted to the root. For example, if you have assets = { directory = "./public/" }, a route like "example.com/blog/*" and a file ./public/blog/logo.png, this will be available at example.com/blog/logo.png. Assets outside of directories which match the configured HTTP routes can still be accessed with the Assets binding or with a Service binding to this Worker.
#7380 72935f9 Thanks @CarmenPopoviciu! - Add Workers + Assets support in wrangler dev --remote

Patch Changes

#7573 fb819f9 Thanks @emily-shen! - feat: add experimental_readRawConfig()

Adds a Wrangler API to find and read a config file
#7549 42b9429 Thanks @penalosa! - Expand metrics collection to:
- Detect Pages & Workers CI
- Filter out default args (e.g. --x-versions, --x-dev-env, and --latest) by only including args that were in argv
#7583 8def8c9 Thanks @penalosa! - Revert support for custom unenv resolve path to address an issue with Wrangler failing to deploy Pages projects with nodejs_compat_v2 in some cases

Open source →

3.97.017 Dec 2024withdrawn: Downgrade to 3.96.0

By default wrangler uses the bundled unenv preset.

Minor Changes

#7522 6403e41 Thanks @vicb! - feat(wrangler): allow overriding the unenv preset.

By default wrangler uses the bundled unenv preset.

Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset. Those paths are used when resolving the unenv module identifiers to absolute paths. This can be used to test a development version.
#7479 2780849 Thanks @penalosa! - Accept a JSON file of the format { name: string }[] in wrangler kv bulk delete, as well as the current string[] format.

Patch Changes

#7541 ca9410a Thanks @vicb! - chore(wrangler): update unenv dependency version
#7345 15aa936 Thanks @edmundhung! - fix(wrangler): keypress event name is optional

Open source →

3.96.016 Dec 2024

Currently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and

Minor Changes

#7510 004af53 Thanks @oliy! - Add file prefix option to wrangler pipelines commands
#7383 8af3365 Thanks @jonesphillip! - Added wrangler r2 domain get command

Patch Changes

#7542 f13c897 Thanks @CarmenPopoviciu! - Always print deployment and placement ID in Cloudchamber commands

Currently, Cloudchamber commands only print the full deployment ID when the deployment has an IPv4 address. This commit ensures the deployment ID and the placement ID are always printed to stdout. It also moves the printing of the IPv4 address (if one exists) to the same place as the IPv6 address so that they are printed together.
#6754 0356d0a Thanks @bluwy! - refactor: move @cloudflare/workers-shared as dev dependency
#7478 2e90efc Thanks @petebacondarwin! - fix: ensure that non-inherited fields are not removed when using an inferred named environment

It is an error for the the user to provide an environment name that doesn't match any of the named environments in the Wrangler configuration. But if there are no named environments defined at all in the Wrangler configuration, we special case the top-level environment as though it was a named environment. Previously, when this happens, we would remove all the nonInheritable fields from the configuration (essentially all the bindings) leaving an incorrect configuration. Now we correctly generate a flattened named environment that has the nonInheritable fields, plus correctly applies any transformFn on inheritable fields.
#7524 11f95f7 Thanks @gpanders! - Include response body in Cloudchamber API errors
#7427 3bc0f28 Thanks @edmundhung! - The x-provision experimental flag now identifies draft and inherit bindings by looking up the current binding settings.

Draft bindings can then be provisioned (connected to new or existing KV, D1, or R2 resources) during wrangler deploy.
Updated dependencies []:
- miniflare@3.20241205.0

Open source →

3.93.06 Dec 2024

For new users, Cloudflare will collect anonymous usage telemetry to guide and improve Wrangler's development. If you have already opted out of Wrangle

Minor Changes

#7291 f5b9cd5 Thanks @edmundhung! - Add anonymous telemetry to Wrangler commands

For new users, Cloudflare will collect anonymous usage telemetry to guide and improve Wrangler's development. If you have already opted out of Wrangler's existing telemetry, this setting will still be respected.

See our data policy for more details on what we collect and how to opt out if you wish.
#7448 20a0f17 Thanks @GregBrimble! - feat: Allow Workers for Platforms scripts (scripts deployed with --dispatch-namespace) to bring along assets
#7445 f4ae6ee Thanks @WillTaylorDev! - Support for assets.experimental_serve_directly with wrangler dev

Patch Changes

#7256 415e5b5 Thanks @jamesopstad! - Export unstable_readConfig function and Unstable_Config, Unstable_RawConfig, Unstable_RawEnvironment and Unstable_MiniflareWorkerOptions types from Wrangler. Overload unstable_getMiniflareWorkerOptions function to accept a config that has already been loaded.
#7431 8f25ebe Thanks @vicb! - chore(wrangler): update unenv dependency version

Pull in:
- refactor(cloudflare): reimplement module:createRequire for latest workerd (unjs/unenv#351)
- refactor: use node:events instead of relative path (unjs/unenv#354)
- refactor(http, cloudflare): use unenv/ imports inside node:http (unjs/unenv#363)
- refactor(node:process): set process.domain to undefined (unjs/unenv#367)
#7426 b40d0ab Thanks @petebacondarwin! - fix: allow the asset directory to be omitted in Wrangler config for commands that don't need it
#7454 f2045be Thanks @petebacondarwin! - refactor: Ensure that unstable type exports are all prefixed with Unstable_ rather than just Unstable
#7461 9ede45b Thanks @petebacondarwin! - fix: relax validation of unsafe configuration to allow an empty object

The types, the default and the code in general support an empty object for this config setting.

So it makes sense to avoid erroring when validating the config.
#7446 9435af0 Thanks @petebacondarwin! - fix: make sure Wrangler doesn't create a .wrangler tmp dir in the functions/ folder of a Pages project

This regression was introduced in https://github.com/cloudflare/workers-sdk/pull/7415 and this change fixes it by reverting that change.
#7385 14a7bc6 Thanks @edmundhung! - The x-provision experimental flag now support inherit bindings in deploys
#7463 073293f Thanks @penalosa! - Clarify messaging around wrangler versions commands to reflect that they're stable (and have been since GA during birthday week)
#7436 5e69799 Thanks @Ankcorn! - Relax type on observability.enabled to remove linting error for nested configurations
#7450 8c873ed Thanks @petebacondarwin! - fix: ensure that version secrets commands do not write wrangler config warnings
Updated dependencies [21a9e24, f4ae6ee]:
- miniflare@3.20241205.0
- @cloudflare/workers-shared@0.10.0

Open source →

3.92.03 Dec 2024

In an npm workspace environment, wrangler will now be able to successfully resolve package exports.

Minor Changes

#7251 80a83bb Thanks @penalosa! - Improve Wrangler's multiworker support to allow running multiple workers at once with one command. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first config will be treated as the primary worker and will be exposed over HTTP as usual (localhost:8787) while the rest will be treated as secondary and will only be accessible via a service binding from the primary worker. Notably, these workers all run in the same runtime instance, which should improve reliability of multiworker dev and fix some bugs (RPC to cross worker Durable Objects, for instance).
#7130 11338d0 Thanks @nickbabcock! - Update import resolution for files and package exports

In an npm workspace environment, wrangler will now be able to successfully resolve package exports.

Previously, wrangler would only be able to resolve modules in a relative node_modules directory and not the workspace root node_modules directory.
#7355 5928e8c Thanks @emily-shen! - feat: add experimental_serve_directly option to Workers with Assets

Users can now specify whether their assets are served directly against HTTP requests or whether these requests always go to the Worker, which can then respond with asset retrieved by its assets binding.

Patch Changes

#7326 24c752e Thanks @OilyLime! - Print wrangler.toml snippet when creating new Hyperdrive Config
#7272 a3f56d1 Thanks @penalosa! - Make debug log for .env not found less scary
#7377 6ecc74e Thanks @edmundhung! - The x-provision experimental flag now skips validation of KV, R2, and D1 IDs in the configuration file.
#7348 4cd8b46 Thanks @edmundhung! - Added x-provision global option

This experimental flag currently has no effect. More details will be shared as we roll out its functionality.
#7381 22a4055 Thanks @penalosa! - Turn on --x-registry for Pages by default
#7360 98d2725 Thanks @emily-shen! - fix: allow running wrangler types when expected entrypoint doesn't exist
Updated dependencies [ac87395, 6b21919, b3d2e7d]:
- miniflare@3.20241106.2
- @cloudflare/workers-shared@0.9.1

Open source →

3.91.026 Nov 2024

Wrangler now supports both JSON (wrangler.json) and TOML (wrangler.toml) for it's configuration file. The format of Wrangler's configuration file is e

Minor Changes

#7230 6fe9533 Thanks @penalosa! - Turn on wrangler.json(c) support by default

Wrangler now supports both JSON (wrangler.json) and TOML (wrangler.toml) for it's configuration file. The format of Wrangler's configuration file is exactly the same across both languages, except that the syntax is JSON rather than TOML. e.g.
```
name = "worker-ts"
main = "src/index.ts"
compatibility_date = "2023-05-04"
```
would be interpreted the same as the equivalent JSON
```
{
  "name": "worker-ts",
  "main": "src/index.ts",
  "compatibility_date": "2023-05-04"
}
```
#7330 219109a Thanks @jonesphillip! - Added Oceania (oc) location hint as acceptable choice when creating an R2 bucket.
#7227 02a0e1e Thanks @taylorlee! - Add preview_urls toggle to wrangler.toml

The current Preview URLs (beta) feature routes to version preview urls based on the status of the workers_dev config value. Beta users have requested the ability to enable deployment urls and preview urls separately on workers.dev, and the new previews_enabled field of the enable-subdomain API will allow that. This change separates the workers_dev and preview_urls behavior during wrangler triggers deploy and wrangler versions upload. preview_urls defaults to true, and does not implicitly depend on routes the way workers_dev does.
#7308 1b1d01a Thanks @gpanders! - Add a default image for cloudchamber create and modify commands
#7232 7da76de Thanks @toddmantell! - feat: implement queues info command

This command allows users to get information on individual queues.

To run this command use the queues info command with the name of a queue in the user's account.

wrangler queues info my-queue-name

Patch Changes

#7319 5a2c93d Thanks @vicb! - chore(wrangler): update unenv dependency version

Pulls in the implementation of module.findSourceMap
Updated dependencies [0d314ed, 476e5df]:
- @cloudflare/workers-shared@0.9.0
- miniflare@3.20241106.1

Open source →

3.89.021 Nov 2024

Updated dependencies [`563439b`]:

Minor Changes

#7252 97acf07 Thanks @Maximo-Guk! - feat: Add production_branch and deployment_trigger to pages deploy detailed artifact for wrangler-action pages parity
#7263 1b80dec Thanks @danielrs! - Fix wrangler pages deployment (list|tail) environment filtering.

Patch Changes

#7314 a30c805 Thanks @Ankcorn! - Fix observability.logs.enabled validation
#7285 fa21312 Thanks @penalosa! - Rename directory to projectRoot and ensure it's relative to the wrangler.toml. This fixes a regression which meant that .wrangler temporary folders were inadvertently generated relative to process.cwd() rather than the location of the wrangler.toml file. It also renames directory to projectRoot, which affects the `unstable_startWorker() interface.
Updated dependencies [563439b]:
- miniflare@3.20241106.1

Open source →

3.88.019 Nov 2024

It also adds the following setting to the logs config

Minor Changes

#7173 b6cbfbd Thanks @Ankcorn! - Adds [observability.logs] settings to wrangler. This setting lets developers control the settings for logs as an independent dataset enabling more dataset types in the future. The most specific setting will win if any of the datasets are not enabled.

It also adds the following setting to the logs config
- invocation_logs - set to false to disable invocation logs. Defaults to true.
```
[observability.logs]
enabled = true
invocation_logs = false
```
#7207 edec415 Thanks @jonesphillip! - Added r2 bucket lifecycle command to Wrangler including list, add, remove, set

Patch Changes

#7243 941d411 Thanks @penalosa! - Include Version Preview URL in Wrangler's output file
#7038 e2e6912 Thanks @petebacondarwin! - fix: only show fetch warning if on old compatibility_date

Now that we have the allow_custom_ports compatibility flag, we only need to show the fetch warnings when that flag is not enabled.

Fixes https://github.com/cloudflare/workerd/issues/2955
#7216 09e6e90 Thanks @vicb! - chore(wrangler): update unenv dependency version
#7081 b4a0e74 Thanks @penalosa! - Default the file based registry (--x-registry) to on. This should improve stability of multi-worker development
Updated dependencies []:
- miniflare@3.20241106.0

Open source →

3.87.014 Nov 2024

You can now configure tail_consumers in conjunction with assets in your wrangler.toml file. Read more about Static Assets and Tail Consumers in the do

Minor Changes

#7201 beed72e Thanks @GregBrimble! - feat: Tail Consumers are now supported for Workers with assets.

You can now configure tail_consumers in conjunction with assets in your wrangler.toml file. Read more about Static Assets and Tail Consumers in the documentation.
#7212 837f2f5 Thanks @jonesphillip! - Added r2 bucket info command to Wrangler. Improved formatting of r2 bucket list output

Patch Changes

#7210 c12c0fe Thanks @taylorlee! - Avoid an unnecessary GET request during wrangler deploy.
#7197 4814455 Thanks @michelheusschen! - fix console output for wrangler d1 migrations create
#6795 94f07ee Thanks @benmccann! - chore: upgrade chokidar to v4
#7133 c46e02d Thanks @gpanders! - Do not emit escape sequences when stdout is not a TTY

Open source →

3.86.08 Nov 2024

Updated dependencies [`1db7846`, `08c6580`]:

Minor Changes

#7154 ef7c0b3 Thanks @jonesphillip! - Added the ability to enable, disable, and get r2.dev public access URLs for R2 buckets.

Patch Changes

#7169 9098a3b Thanks @penalosa! - Ensure workerd processes are cleaned up after address-in-use errors
#7172 3dce388 Thanks @penalosa! - Clarify dev registry messaging around locally connected services. The connection status of local service bindings & durable object bindings is now indicated by connected or not connected next to their entry in the bindings summary. For more details, refer to https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/#local-development
#7193 ad51d1d Thanks @sdnts! - Output suggested wrangler.toml changes after creating an R2 bucket
#7191 1d5bc6d Thanks @sdnts! - Output suggested wrangler.toml changes after creating a Queue
Updated dependencies [1db7846, 08c6580]:
- miniflare@3.20241106.0
- @cloudflare/workers-shared@0.7.1

Open source →

3.85.06 Nov 2024

### Minor Changes - #7105 `a5f1779` Thanks @jonesphillip! - Added the ability to list, add, remove, and update R2 bucket custom domains. - #7132 `89f6

Minor Changes

#7105 a5f1779 Thanks @jonesphillip! - Added the ability to list, add, remove, and update R2 bucket custom domains.
#7132 89f6274 Thanks @gabivlj! - Event messages are capitalized, images of wrong architectures properly show the error in cloudchamber create When a new "health" enum is introduced, wrangler cloudchamber list won't crash anymore. Update Cloudchamber schemas.
#7121 2278616 Thanks @bruxodasilva! - Added pause and resume commands to manage Workflows and hidded unimplemented delete command

Patch Changes

#7134 3ee1353 Thanks @cmackenzie1! - Change Pipelines to use name instead of ID
#7020 e1d2fd6 Thanks @KianNH! - chore: move printWranglerBanner for secret delete into handler
#7150 6380d86 Thanks @emily-shen! - refactor: improve login/logout/whoami setup with the new internal registration utils
#6756 49ef163 Thanks @WalshyDev! - chore: disable wrangler.toml warnings when doing wrangler login & wrangler logout
#7164 1bd4885 Thanks @penalosa! - Fix --test-scheduled with custom builds & --x-dev-env

Open source →

3.84.030 Oct 2024

both hyperdrive create and hyperdrive update now support updating configs with connection strings.

Minor Changes

#6999 0111edb Thanks @garvit-gupta! - docs: Vectorize GA Announcement Banner
#6916 a33a133 Thanks @garrettgu10! - Local development now supports Vectorize bindings
#7004 15ef013 Thanks @garvit-gupta! - feat: Enable Vectorize query by id via Wrangler
#7092 038fdd9 Thanks @jonesphillip! - Added location hint option for the Wrangler R2 bucket create command
#7024 bd66d51 Thanks @xortive! - feature: allow using a connection string when updating hyperdrive configs

both hyperdrive create and hyperdrive update now support updating configs with connection strings.

Patch Changes

#7091 68a2a84 Thanks @taylorlee! - fix: synchronize observability settings during wrangler versions deploy

When running wrangler versions deploy, Wrangler will now update observability settings in addition to logpush and tail_consumers. Unlike wrangler deploy, it will not disable observability when observability is undefined in wrangler.toml.
#7080 924ec18 Thanks @vicb! - chore(wrangler): update unenv dependency version
#7097 8ca4b32 Thanks @emily-shen! - fix: remove deprecation warnings for wrangler init

We will not be removing wrangler init (it just delegates to create-cloudflare now). These warnings were causing confusion for users as it wrangler init is still recommended in many places.
#7073 656a444 Thanks @penalosa! - Internal refactor to remove es-module-lexer and support wrangler types for Workers with Durable Objects & JSX
#7024 bd66d51 Thanks @xortive! - fix: make individual parameters work for wrangler hyperdrive create when not using HoA

wrangler hyperdrive create individual parameters were not setting the database name correctly when calling the api.
#7024 bd66d51 Thanks @xortive! - refactor: use same param parsing code for wrangler hyperdrive create and wrangler hyperdrive update

ensures that going forward, both commands support the same features and have the same names for config flags

Open source →

3.83.024 Oct 2024

This also adds an id option to allow users to optionally customize the new instance id.

Minor Changes

#7000 1de309b Thanks @jkoe-cf! - feature: allowing users to specify a description when creating an event notification rule

Patch Changes

#7011 cef32c8 Thanks @GregBrimble! - fix: Correctly apply Durable Object migrations for namespaced scripts
#7067 4aa35c5 Thanks @LuisDuarte1! - Change trigger command to comply with the current workflows endpoint.

This also adds an id option to allow users to optionally customize the new instance id.
#7082 3f1d79c Thanks @LuisDuarte1! - Change to new terminate instance workflow endpoint
#7036 e7ea600 Thanks @penalosa! - Reduce KV bulk upload bucket size to 1000 (from the previous 5000)
#7068 a2afcf1 Thanks @RamIdeas! - log warning of Workflows open-beta status when running deploying a Worker that contains a Workflow binding
#7065 b219296 Thanks @penalosa! - Internal refactor to remove React/ink from all non-wrangler dev flows
#7064 a90980c Thanks @penalosa! - Fix wrangler dev --remote --show-interactive-dev-session=false by only enabling hotkeys after account selection if hotkeys were previously enabled
#7045 5ef6231 Thanks @RamIdeas! - Add preliminary support for Workflows in wrangler dev
#7075 80e5bc6 Thanks @LuisDuarte1! - Fix params serialization when send the trigger workflow API

Previously, wrangler did not parse the params sending it as a string to workflow's services.
Updated dependencies [760e43f, 8dc2b7d, 5ef6231]:
- miniflare@3.20241022.0
- @cloudflare/workers-shared@0.7.0

Open source →

3.82.022 Oct 2024

To bind to a workflow, add a workflows section in your wrangler.toml:

Minor Changes

#6945 6b97353 Thanks @bthwaites! - Add jurisdiction option to R2 event notification wrangler actions

Patch Changes

#5737 9bf51d6 Thanks @penalosa! - Validate duplicate bindings across all binding types
#7010 1f6ff8b Thanks @vicb! - chore: update unenv dependency version
#7012 244aa57 Thanks @RamIdeas! - Add support for Workflow bindings (in deployments, not yet in local dev)

To bind to a workflow, add a workflows section in your wrangler.toml:
```
[[workflows]]
binding = "WORKFLOW"
name = "my-workflow"
class_name = "MyDemoWorkflow"
```
and export an entrypoint (e.g. MyDemoWorkflow) in your script:
```
import { WorkflowEntrypoint } from "cloudflare:workers";

export class MyDemoWorkflow extends WorkflowEntrypoint<Env, Params> {...}
```
#7039 e44f496 Thanks @penalosa! - Only show dev registry connection status in local dev
#7037 e1b93dc Thanks @emily-shen! - fix: ask for confirmation before creating a new Worker when uploading secrets

Previously, wrangler secret put KEY --name non-existent-worker would automatically create a new Worker with the name non-existent-worker. This fix asks for confirmation before doing so (if running in an interactive context). Behaviour in non-interactive/CI contexts should be unchanged.
#7015 48152d6 Thanks @RamIdeas! - add wrangler workflows ... commands
#7041 045787b Thanks @CarmenPopoviciu! - Show wrangler pages dev --proxy warning

On Node.js 17+, wrangler will default to fetching only the IPv6 address. With these changes we warn users that the process listening on the port specified via --proxy should be configured for IPv6.
#7018 127615a Thanks @emily-shen! - fix: log successful runs of d1 execute in local
#6970 a8ca700 Thanks @oliy! - Add HTTP authentication options for Workers Pipelines
#7005 6131ef5 Thanks @edmundhung! - fix: prevent users from passing multiple arguments to non array options
#7046 f9d5fdb Thanks @oliy! - Minor change to 3rd party API shape for Workers Pipelines
#6972 c794935 Thanks @penalosa! - Add (local) indicator to bindings using local data
Updated dependencies [809193e]:
- miniflare@3.20241018.0

Open source →

3.80.310 Oct 2024

Pulls in feat(node/net): implement Server mock.

Patch Changes

#6927 2af75ed Thanks @emily-shen! - fix: respect CLOUDFLARE_ACCOUNT_ID with wrangler pages project commands

Fixes #4947
#6894 eaf71b8 Thanks @petebacondarwin! - fix: improve the rendering of build errors when bundling
#6920 2e64968 Thanks @vicb! - chore: update unenv dependency version

Pulls in feat(node/net): implement Server mock.
#6932 4c6aad0 Thanks @vicb! - fix: allow requireing unenv aliased packages

Before this PR requireing packages aliased in unenv would fail. That's because require would load the mjs file.

This PR adds wraps the mjs file in a virtual ES module to allow requireing it.

Open source →

3.80.17 Oct 2024

Fixes #5768 - issue with vitest and Pages projects with wrangler.toml

Patch Changes

#6908 d696850 Thanks @penalosa! - fix: debounce restarting worker on assets dir file changes when --x-dev-env is enabled.
#6902 dc92af2 Thanks @threepointone! - fix: enable esbuild's keepNames: true to set .name on functions/classes
#6909 82180a7 Thanks @penalosa! - fix: Various fixes for logging in --x-dev-env, primarily to ensure the hotkeys don't wipe useful output and are cleaned up correctly
#6903 54924a4 Thanks @petebacondarwin! - fix: ensure that alias config gets passed through to the bundler when using new --x-dev-env

Fixes #6898
#6911 30b7328 Thanks @emily-shen! - fix: infer experimentalJsonConfig from file extension

Fixes #5768 - issue with vitest and Pages projects with wrangler.toml
Updated dependencies [5c50949]:
- miniflare@3.20240925.1

Open source →

3.80.04 Oct 2024

If you experience any issues, you can disable the flag with --x-dev-env=false. Please also let us know by opening an issue at https://github.com/cloud

Minor Changes

#6408 3fa846e Thanks @RamIdeas! - feat: update the --experimental-dev-env (shorthand: --x-dev-env) flag to on-by-default

If you experience any issues, you can disable the flag with --x-dev-env=false. Please also let us know by opening an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose.

Patch Changes

#6854 04a8fed Thanks @penalosa! - chore: Include serialised FormData in debug logs
#6879 b27d8cb Thanks @petebacondarwin! - fix: the docs command should not crash if given search terms

Fixes a regression accidentally introduced by #3735.
#6873 b123f43 Thanks @zwily! - fix: reduce logging noise during wrangler dev with static assets

Updates to static assets are accessible by passing in --log-level="debug" but otherwise hidden.
#6881 7ca37bc Thanks @RamIdeas! - fix: custom builds outputting files in assets watched directory no longer cause the custom build to run again in an infinite loop
#6872 b2d094e Thanks @petebacondarwin! - fix: render a helpful build error if a Service Worker mode Worker has imports

A common mistake is to forget to export from the entry-point of a Worker, which causes Wrangler to infer that we are in "Service Worker" mode.

In this mode, imports to external modules are not allowed. Currently this only fails at runtime, because our esbuild step converts these imports to an internal __require() call that throws an error. The error message is misleading and does not help the user identify the cause of the problem. This is particularly tricky where the external imports are added by a library or our own node.js polyfills.

Fixes #6648
#6792 27e8385 Thanks @penalosa! - fix: Handle more module declaration cases
#6838 7dbd0c8 Thanks @GregBrimble! - fix: Improve static asset upload messaging

Open source →

3.78.925 Sept 2024

### Patch Changes - #6753 `4e33f2c` Thanks @bluwy! - refactor: prevent bundling entire package.json in built code - #6812 `f700d37` Thanks @CarmenPopo

Patch Changes

#6753 4e33f2c Thanks @bluwy! - refactor: prevent bundling entire package.json in built code
#6812 f700d37 Thanks @CarmenPopoviciu! - fix: Validate additional config properties for [observability]
#6751 638a550 Thanks @bluwy! - refactor: simplify date calculation and remove date-fns dependency
#6809 28cb0d7 Thanks @smellercf! - fix: Remove Beta tag from r2 event notification wrangler command descriptions
#6802 17eb8a9 Thanks @CarmenPopoviciu! - chore: rename experimental_assets to assets
#6781 0792fa0 Thanks @mikenomitch! - chore: tweaks warning when using node_compat

Open source →

3.78.720 Sept 2024

This commit fixes the current behaviour of watch mode for Workers with assets, and adds support for switching between static and dynamic Workers withi

Patch Changes

#6775 ecd82e8 Thanks @CarmenPopoviciu! - fix: Support switching between static and dynamic Workers

This commit fixes the current behaviour of watch mode for Workers with assets, and adds support for switching between static and dynamic Workers within a single wrangler dev session.
#6762 2840b9f Thanks @petebacondarwin! - fix: error if a user inadvertently uploads a Pages _workers.js file or directory as an asset
#6778 61dd93a Thanks @CarmenPopoviciu! - fix: Error if Workers + Assets are run in remote mode

Workers + Assets are currently supported only in local mode. We should throw an error if users attempt to use Workers with assets in remote mode.
#6782 7655505 Thanks @vicb! - chore: update unenv dependency version
#6777 9649dbc Thanks @penalosa! - chore: Update CI messaging
#6779 3e75612 Thanks @emily-shen! - fix: include asset binding in wrangler types

Open source →

3.78.518 Sept 2024

Tail Workers are currently not supported for Workers with assets. This commit ensures we throw a corresponding error if users are attempting to config

Patch Changes

#6744 e3136f9 Thanks @petebacondarwin! - chore: update unenv dependency version
#6749 9a06f88 Thanks @CarmenPopoviciu! - fix: Throw error when attempting to configure Workers with assets and tail consumers

Tail Workers are currently not supported for Workers with assets. This commit ensures we throw a corresponding error if users are attempting to configure tail_consumers via their configuration file, for a Worker with assets. This validation is applied for all wrangler dev, wrangler deploy, wrangler versions upload.
#6746 0deb42b Thanks @GregBrimble! - fix: Fix assets upload message to correctly report number of uploaded assets
#6745 6dbbb88 Thanks @jonesphillip! - fix: r2 bucket notification get <bucket_name> has been marked deprecated in favor of r2 bucket notification list <bucket_name> to reflect behavior.
Updated dependencies [2407c41]:
- miniflare@3.20240909.3

Open source →

wrangler

Release timeline

Releases

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Example

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Affected commands

Config redirect file

Custom build tool example

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes