Wrangler Changelog

2024-01-26

3.25.0

#4815 030360d6 Thanks @jonesphillip! - feature: adds support for configuring Sippy with Google Cloud Storage (GCS) provider.
Sippy (https://developers.cloudflare.com/r2/data-migration/sippy/) now supports Google Cloud Storage. This change updates the wrangler r2 sippy commands to take a provider (AWS or GCS) and appropriate configuration arguments. If you don’t specify --provider argument then the command will enter an interactive flow for the user to set the configuration. Note that this is a breaking change from the previous behaviour where you could configure AWS as the provider without explictly specifying the --provider argument. (This breaking change is allowed in a minor release because the Sippy feature and wrangler r2 sippy commands are marked as beta.)
#4841 10396125 Thanks @rozenmd! - fix: replace D1’s dashed time-travel endpoints with underscored ones
D1 will maintain its d1/database/${databaseId}/time-travel/* endpoints until GA, at which point older versions of wrangler will start throwing errors to users, asking them to upgrade their wrangler version to continue using Time Travel via CLI.
#4656 77b0bce3 Thanks @petebacondarwin! - fix: ensure upstream_protocol is passed to the Worker
In wrangler dev it is possible to set the upstream_protocol, which is the protocol under which the User Worker believes it has been requested, as recorded in the request.url that can be used for forwarding on requests to the origin.
Previously, it was not being passed to wrangler dev in local mode. Instead it was always set to http.
Note that setting upstream_protocol to http is not supported in wrangler dev remote mode, which is the case since Wrangler v2.0.
This setting now defaults to https in remote mode (since that is the only option), and to the same as local_protocol in local mode.
Fixes #4539
#4810 6eb2b9d1 Thanks @gabivlj! - fix: Cloudchamber command shows json error message on load account if –json specified
If the user specifies a json option, we should see a more detailed error on why loadAccount failed.
#4820 b01c1548 Thanks @mrbbot! - fix: show up-to-date sources in DevTools when saving source files
Previously, DevTools would never refresh source contents after opening a file, even if it was updated on-disk. This could cause issues with step-through debugging as breakpoints set in source files would map to incorrect locations in bundled Worker code. This change ensures DevTools’ source cache is cleared on each reload, preventing outdated sources from being displayed.
Updated dependencies [ 8166eefc]:
- miniflare@3.20231218.4

2024-01-23

3.24.0

#4523 9f96f28b Thanks @dario-piotrowicz! - Add new getBindingsProxy utility to the wrangler package
The new utility is part of wrangler’s JS API (it is not part of the wrangler CLI) and its use is to provide proxy objects to bindings, such objects can be used in Node.js code as if they were actual bindings
The utility reads the wrangler.toml file present in the current working directory in order to discern what bindings should be available (a wrangler.json file can be used too, as well as config files with custom paths).
Example
Assuming that in the current working directory there is a wrangler.toml file with the following content:
```
[[kv_namespaces]]
binding = "MY_KV"
id = "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
```
The utility could be used in a nodejs script in the following way:
```
import { getBindingsProxy } from "wrangler";

const { bindings, dispose } = await getBindingsProxy();

try {	const myKv = bindings.MY_KV;	const kvValue = await myKv.get("my-kv-key");
	console.log(`KV Value = ${kvValue}`);
} finally {	await dispose();
}
```
#3427 b79e93a3 Thanks @ZakKemble! - fix: Use Windows SYSTEMROOT env var for finding netstat
Currently, the drive letter of os.homedir() (the user’s home directory) is used to build the path to netstat.exe. However, user directories are not always on the same drive as the Windows installation, in which case the path to netstat will be incorrect. Now we use the %SYSTEMROOT% environment variable which correctly points to the installation path of Windows.
#4768 c3e410c2 Thanks @petebacondarwin! - ci: bump undici versions to 5.28.2
Updated dependencies [ c3e410c2]:
- miniflare@3.20231218.3

2024-01-18

3.23.0

#4310 dae30015 Thanks @gabivlj! - Added wrangler cloudchamber commands
See #4310 for more details.
#4674 54ea6a53 Thanks @matthewdavidrodgers! - Fix usage of patch API in bulk secrets update
Only specifying the name and type of a binding instructs the patch API to copy the existing binding over - but we were including the contents of the binding as well. Normally that’s OK, but there are some subtle differences between what you specify to create a binding vs what it looks like once it’s created, specifically for Durable Objects. So instead, we just use the simpler inheritance.
#4772 4a9f03cf Thanks @mrbbot! - fix: ensure dev server doesn’t change request URLs
Previously, Wrangler’s dev server could change incoming request URLs unexpectedly (e.g. rewriting http://localhost:8787//test to http://localhost:8787/test). This change ensures URLs are passed through without modification.
Fixes #4743.

2.21.0

#4765 2732007d Thanks @mrbbot! - chore: bump miniflare to 2.14.2

2024-01-16

3.22.5

#4707 96a27f3d Thanks @mrbbot! - fix: only offer to report unknown errors
Previously, Wrangler would offer to report any error to Cloudflare. This included errors caused by misconfigurations or invalid commands. This change ensures those types of errors aren’t reported.
#4676 078cf84d Thanks @dario-piotrowicz! - make sure the script path is correctly resolved in pages dev when no directory is specified
#4722 5af6df13 Thanks @mrbbot! - fix: don’t require auth for wrangler r2 object --local operations
Previously, Wrangler would ask you to login when reading or writing from local R2 buckets. This change ensures no login prompt is displayed, as authentication isn’t required for these operations.
#4719 c37d94b5 Thanks @mrbbot! - fix: ensure miniflare and wrangler can source map in the same process
Previously, if in a wrangler dev session you called console.log() and threw an unhandled error you’d see an error like [ERR_ASSERTION]: The expression evaluated to a falsy value. This change ensures you can do both of these things in the same session.
#4683 24147166 Thanks @mrbbot! - fix: ensure logs containing at not truncated to at [object Object]
Previously, logs containing at were always treated as stack trace call sites requiring source mapping. This change updates the call site detection to avoid false positives.
#4748 3603a60d Thanks @Cherry! - fix: resolve imports in a more node-like fashion for packages that do not declare exports
Previously, trying to import a file that wasn’t explicitly exported from a module would result in an error, but now, better attempts are made to resolve the import using node’s module resolution algorithm. It’s now possible to do things like this:
```
import JPEG_DEC_WASM from "@jsquash/jpeg/codec/dec/mozjpeg_dec.wasm";
```
This works even if the mozjpeg_dec.wasm file isn’t explicitly exported from the @jsquash/jpeg module.
Fixes #4726
#4687 0a488f66 Thanks @mrbbot! - fix: remove confusing --local messaging from wrangler pages dev
Running wrangler pages dev would previously log a warning saying --local is no longer required even though --local was never set. This change removes this warning.
Updated dependencies [ 4f6999ea, c37d94b5]:
- miniflare@3.20231218.2

2024-01-09

3.22.4

#4699 4b4c1416 Thanks @mrbbot! - fix: prevent repeated reloads with circular service bindings
wrangler@3.19.0 introduced a bug where starting multiple wrangler dev sessions with service bindings to each other resulted in a reload loop. This change ensures Wrangler only reloads when dependent wrangler dev sessions start/stop.

2024-01-04

3.22.3

#4693 93e88c43 Thanks @mrbbot! - fix: ensure wrangler dev exits with code 0 on clean exit
Previously, wrangler dev would exit with a non-zero exit code when pressing CTRL+C or x. This change ensures wrangler exits with code 0 in these cases.
#4630 037de5ec Thanks @petebacondarwin! - fix: ensure User Worker gets the correct Host header in wrangler dev local mode
Some full-stack frameworks, such as Next.js, check that the Host header for a server side action request matches the host where the application is expected to run.
In wrangler dev we have a Proxy Worker in between the browser and the actual User Worker. This Proxy Worker is forwarding on the request from the browser, but then the actual User Worker is running on a different host:port combination than that which the browser thinks it should be on. This was causing the framework to think the request is malicious and blocking it.
Now we update the request’s Host header to that passed from the Proxy Worker in a custom MF-Original-Url header, but only do this if the request also contains a shared secret between the Proxy Worker and User Worker, which is passed via the MF-Proxy-Shared-Secret header. This last feature is to prevent a malicious website from faking the Host header in a request directly to the User Worker.
Fixes https://github.com/cloudflare/next-on-pages/issues/588
#4695 0f8a03c0 Thanks @mrbbot! - fix: ensure API failures without additional messages logged correctly
#4693 93e88c43 Thanks @mrbbot! - fix: ensure wrangler pages dev exits cleanly
Previously, pressing CTRL+C or x when running wrangler pages dev wouldn’t actually exit wrangler. You’d need to press CTRL+C a second time to exit the process. This change ensures wrangler exits the first time.
#4696 624084c4 Thanks @mrbbot! - fix: include additional modules in largest dependencies warning
If your Worker fails to deploy because it’s too large, Wrangler will display of list of your Worker’s largest dependencies. Previously, this just included JavaScript dependencies. This change ensures additional module dependencies (e.g. WebAssembly, text blobs, etc.) are included when computing this list.
Updated dependencies [ 037de5ec]:
- miniflare@3.20231218.1

2024-01-02

3.22.2

#4600 4233e514 Thanks @mrbbot! - fix: apply source mapping to deployment validation errors
Previously if a Worker failed validation during wrangler deploy, the displayed error would reference locations in built JavaScript files. This made it more difficult to debug validation errors. This change ensures these errors are now source mapped, referencing locations in source files instead.
#4440 15717333 Thanks @mrbbot! - fix: automatically create required directories for wrangler r2 object get
Previously, if you tried to use wrangler r2 object get with an object name containing a / or used the --file flag with a path containing a /, and the specified directory didn’t exist, Wrangler would throw an ENOENT error. This change ensures Wrangler automatically creates required parent directories if they don’t exist.
#4592 20da658e Thanks @mrbbot! - fix: throw helpful error if email validation required
Previously, Wrangler would display the raw API error message and code if email validation was required during wrangler deploy. This change ensures a helpful error message is displayed instead, prompting users to check their emails or visit the dashboard for a verification link.
#4597 e1d50407 Thanks @mrbbot! - fix: suggest checking permissions on authentication error with API token set
#4593 c370026d Thanks @mrbbot! - fix: include messages from API in errors
#4588 4e5ed0b2 Thanks @mrbbot! - fix: require worker name for rollback
Previously, Wrangler would fail with a cryptic error if you tried to run wrangler rollback outside of a directory containing a Wrangler configuration file with a name defined. This change validates that a worker name is defined, and allows you to set it from the command line using the --name flag.
Updated dependencies [ c410ea14]:
- miniflare@3.20231218.0

2023-12-20

3.22.1

#4635 5bc2699d Thanks @mrbbot! - fix: prevent zombie workerd processes
Previously, running wrangler dev would leave behind “zombie” workerd processes. These processes prevented the same port being bound if wrangler dev was restarted and sometimes consumed lots of CPU time. This change ensures all workerd processes are killed when wrangler dev is shutdown.
To clean-up existing zombie processes, run pkill -KILL workerd on macOS/Linux or taskkill /f /im workerd.exe on Windows.

2023-12-19

3.22.0

#4632 a6a4e8a4 Thanks @G4brym! - Deprecate constellation commands and add a warning when using the constellation binding
#4130 e8a2a1d9 Thanks @vkrasnov! - Added support for R2 Sippy incremental migration
#4621 98dee932 Thanks @rozenmd! - feat: add rows written/read in the last 24 hours to wrangler d1 info output
#4426 c628de59 Thanks @OilyLime! - Improve queues list displaying as table, update queues API types

2023-12-15

3.21.0

#4423 a94ef570 Thanks @mrbbot! - feat: apply source mapping to logged strings
Previously, Wrangler would only apply source mapping to uncaught exceptions. This meant if you caught an exception and logged its stack trace, the call sites would reference built JavaScript files as opposed to source files. This change looks for stack traces in logged messages, and tries to source map them.
Note source mapping is only applied when outputting logs. Error#stack does not return a source mapped stack trace. This means the actual runtime value of new Error().stack and the output from console.log(new Error().stack) may be different.
#4511 66394681 Thanks @huw! - Add ’took recursive isolate lock’ warning to workerd output exceptions

2.20.2

#4609 c228c912 Thanks @mrbbot! - fix: pin workerd to 1.20230404.0
#4587 49a46960 Thanks @mrbbot! - Change dev registry and inspector server to listen on 127.0.0.1 instead of all interfaces
#4587 49a46960 Thanks @mrbbot! - fix: validate Host and Orgin headers where appropriate
Host and Origin headers are now checked when connecting to the inspector proxy. If these don’t match what’s expected, the request will fail.

Wrangler Changelog

​​ 2024-01-26

​​ 3.25.0

​​ 2024-01-23

​​ 3.24.0

​​ Example

​​ 2024-01-18

​​ 3.23.0

​​ 2.21.0

​​ 2024-01-16

​​ 3.22.5

​​ 2024-01-09

​​ 3.22.4

​​ 2024-01-04

​​ 3.22.3

​​ 2024-01-02

​​ 3.22.2

​​ 2023-12-20

​​ 3.22.1

​​ 2023-12-19

​​ 3.22.0

​​ 2023-12-15

​​ 3.21.0

​​ 2.20.2

2024-01-26

3.25.0

2024-01-23

3.24.0

Example

2024-01-18

3.23.0

2.21.0

2024-01-16

3.22.5

2024-01-09

3.22.4

2024-01-04

3.22.3

2024-01-02

3.22.2

2023-12-20

3.22.1

2023-12-19

3.22.0

2023-12-15

3.21.0

2.20.2