chore(deps): update dependency wrangler to v3.18.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
wrangler (source)	3.14.0 -> 3.18.0

---

Release Notes

cloudflare/workers-sdk (wrangler)

v3.18.0

Compare Source

Minor Changes

• #​4532 311ffbd5 Thanks @​mrbbot! - fix: change wrangler (pages) dev to listen on localhost by default

  Previously, Wrangler listened on all interfaces (*) by default. This change switches wrangler (pages) dev to just listen on local interfaces. Whilst this is technically a breaking change, we've decided the security benefits outweigh the potential disruption caused. If you need to access your dev server from another device on your network, you can use wrangler (pages) dev --ip * to restore the previous behaviour.

Patch Changes

• Updated dependencies [1b348782]:
  • [email protected]

v3.17.1

Compare Source

Patch Changes

• #​4474 382ef8f5 Thanks @​mrbbot! - fix: open browser to correct url pressing b in --remote mode

  This change ensures Wrangler doesn't try to open http://* when * is used as the dev server's hostname. Instead, Wrangler will now open http://127.0.0.1.

• #​4488 3bd57238 Thanks @​RamIdeas! - Changes the default directory for log files to workaround frameworks that are watching the entire .wrangler directory in the project root for changes

  Also includes a fix for commands with --json where the log file location message would cause stdout to not be valid JSON. That message now goes to stderr.

v3.17.0

Compare Source

Minor Changes

• #​4341 d9908743 Thanks @​RamIdeas! - Wrangler now writes all logs to a .log file in the .wrangler directory. Set a directory or specific .log filepath to write logs to with WRANGLER_LOG_PATH=../Desktop/my-logs/ or WRANGLER_LOG_PATH=../Desktop/my-logs/my-log-file.log. When specifying a directory or using the default location, a filename with a timestamp is used.

  Wrangler now filters workerd stdout/stderr and marks unactionable messages as debug logs. These debug logs are still observable in the debug log file but will no longer show in the terminal by default without the user setting the env var WRANGLER_LOG=debug.

Patch Changes

• #​4469 d5e1966b Thanks @​mrbbot! - fix: report correct line and column numbers when source mapping errors with wrangler dev --remote

• #​4455 1747d215 Thanks @​rozenmd! - fix: make it possible to ignore hyperdrive warnings

• #​4456 805d5241 Thanks @​dario-piotrowicz! - add warnings about ai and verctorize bindings not being supported locally

• #​4478 7b54350b Thanks @​penalosa! - Don't log sensitive data to the Wrangler debug log file by default. This includes API request headers and responses.

• Updated dependencies [be2b9cf5, d9908743]:

  • [email protected]

v3.16.0

Compare Source

Minor Changes

• #​4347 102e15f9 Thanks @​Skye-31! - Feat(unstable_dev): Provide an option for unstable_dev to perform the check that prompts users to update wrangler, defaulting to false. This will prevent unstable_dev from sending a request to NPM on startup to determine whether it needs to be updated.

• #​4179 dd270d00 Thanks @​matthewdavidrodgers! - Simplify secret:bulk api via script settings

  Firing PUTs to the secret api in parallel has never been a great solution - each request independently needs to lock the script, so running in parallel is at best just as bad as running serially.

  Luckily, we have the script settings PATCH api now, which can update the settings for a script (including secret bindings) at once, which means we don't need any parallelization. However this api doesn't work with a partial list of bindings, so we have to fetch the current bindings and merge in with the new secrets before PATCHing. We can however just omit the value of the binding (i.e. only provide the name and type) which instructs the config service to inherit the existing value, which simplifies this as well. Note that we don't use the bindings in your current wrangler.toml, as you could be in a draft state, and it makes sense as a user that a bulk secrets update won't update anything else. Instead, we use script settings api again to fetch the current state of your bindings.

  This simplified implementation means the operation can only fail or succeed, rather than succeeding in updating some secrets but failing for others. In order to not introduce breaking changes for logging output, the language around "${x} secrets were updated" or "${x} secrets failed" is kept, even if it doesn't make much sense anymore.

Patch Changes

• #​4402 baa76e77 Thanks @​rozenmd! - This PR adds a fetch handler that uses page, assuming result_info provided by the endpoint contains page, per_page, and total

  This is needed as the existing fetchListResult handler for fetching potentially paginated results doesn't work for endpoints that don't implement cursor.

  Fixes #​4349

• #​4337 6c8f41f8 Thanks @​Skye-31! - Improve the error message when a script isn't exported a Durable Object class

  Previously, wrangler would error with a message like Uncaught TypeError: Class extends value undefined is not a constructor or null. This improves that messaging to be more understandable to users.

• #​4307 7fbe1937 Thanks @​jspspike! - Change local dev server default ip to * instead of 0.0.0.0. This will cause the dev server to listen on both ipv4 and ipv6 interfaces

• #​4222 f867e01c Thanks @​tmthecoder! - Support for hyperdrive bindings in local wrangler dev

• #​4149 7e05f38e Thanks @​jspspike! - Fixed issue with tail not using proxy

• #​4219 0453b447 Thanks @​maxwellpeterson! - Allows uploads with both cron triggers and smart placement enabled

• #​4437 05b1bbd2 Thanks @​jspspike! - Change dev registry and inspector server to listen on 127.0.0.1 instead of all interfaces

• Updated dependencies [4f8b3420, 16cc2e92, 3637d97a, 29a59d4e, 7fbe1937, 76787861, 8a25b7fb]:

  • [email protected]

v3.15.0

Compare Source

Minor Changes

• #​4201 0cac2c46 Thanks @​penalosa! - Callout --minify when script size is too large

• #​4209 24d1c5cf Thanks @​mrbbot! - fix: suppress compatibility date fallback warnings if no wrangler update is available

  If a compatibility date greater than the installed version of workerd was
  configured, a warning would be logged. This warning was only actionable if a new
  version of wrangler was available. The intent here was to warn if a user set
  a new compatibility date, but forgot to update wrangler meaning changes
  enabled by the new date wouldn't take effect. This change hides the warning if
  no update is available.

  It also changes the default compatibility date for wrangler dev sessions
  without a configured compatibility date to the installed version of workerd.
  This previously defaulted to the current date, which may have been unsupported
  by the installed runtime.

• #​4135 53218261 Thanks @​Cherry! - feat: resolve npm exports for file imports

  Previously, when using wasm (or other static files) from an npm package, you would have to import the file like so:

  import wasm from "../../node_modules/svg2png-wasm/svg2png_wasm_bg.wasm";

  This update now allows you to import the file like so, assuming it's exposed and available in the package's exports field:

  import wasm from "svg2png-wasm/svg2png_wasm_bg.wasm";

  This will look at the package's exports field in package.json and resolve the file using resolve.exports.

• #​4232 69b43030 Thanks @​romeupalos! - fix: use zone_name to determine a zone when the pattern is a custom hostname

  In Cloudflare for SaaS, custom hostnames of third party domain owners can be used in Cloudflare.
  Workers are allowed to intercept these requests based on the routes configuration.
  Before this change, the same logic used by wrangler dev was used in wrangler deploy, which caused wrangler to fail with:

  ✘ [ERROR] Could not find zone for [partner-saas-domain.com]

• #​4198 b404ab70 Thanks @​penalosa! - When uploading additional modules with your worker, Wrangler will now report the (uncompressed) size of each individual module, as well as the aggregate size of your Worker

Patch Changes

• #​4215 950bc401 Thanks @​RamIdeas! - fix various logging of shell commands to correctly quote args when needed

• #​4274 be0c6283 Thanks @​jspspike! - chore: bump miniflare to 3.20231025.0

  This change enables Node-like console.log()ing in local mode. Objects with
  lots of properties, and instances of internal classes like Request, Headers,
  ReadableStream, etc will now be logged with much more detail.

• #​4127 3d55f965 Thanks @​mrbbot! - fix: store temporary files in .wrangler

  As Wrangler builds your code, it writes intermediate files to a temporary
  directory that gets cleaned up on exit. Previously, Wrangler used the OS's
  default temporary directory. On Windows, this is usually on the C: drive.
  If your source code was on a different drive, our bundling tool would generate
  invalid source maps, breaking breakpoint debugging. This change ensures
  intermediate files are always written to the same drive as sources. It also
  ensures unused build outputs are cleaned up when running wrangler pages dev.

  This change also means you no longer need to set cwd and
  resolveSourceMapLocations in .vscode/launch.json when creating an attach
  configuration for breakpoint debugging. Your .vscode/launch.json should now
  look something like...

  {
  	"configurations": [
  		{
  			"name": "Wrangler",
  			"type": "node",
  			"request": "attach",
  			"port": 9229,
  			// These can be omitted, but doing so causes silent errors in the runtime
  			"attachExistingChildren": false,
  			"autoAttachChildProcesses": false
  		}
  	]
  }

• #​4189 05798038 Thanks @​gabivlj! - Move helper cli files of C3 into @​cloudflare/cli and make Wrangler and C3 depend on it

• #​4235 46cd2df5 Thanks @​mrbbot! - fix: ensure console.log()s during startup are displayed

  Previously, console.log() calls before the Workers runtime was ready to
  receive requests wouldn't be shown. This meant any logs in the global scope
  likely weren't visible. This change ensures startup logs are shown. In particular,
  this should fix Remix's HMR,
  which relies on startup logs to know when the Worker is ready.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://4256649d.guild-dev-website.pages.dev