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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
wrangler (source)	3.93.0 -> 3.101.0

---

Release Notes

cloudflare/workers-sdk (wrangler)

v3.101.0

Compare Source

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

v3.100.0

Compare Source

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 unjs/unenv#378.
  That bug prevented us from using unenv module resolution,
  see #​7583.

• Updated dependencies [b4e0af1]:

  • miniflare@3.20241230.0

v3.99.0

Compare Source

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

v3.98.0

Compare Source

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

v3.97.0

Compare Source

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

v3.96.0

Compare Source

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

v3.95.0

Compare Source

Minor Changes

• #​7382 e0b98fd Thanks @​jonesphillip! - Added r2 bucket cors command to Wrangler including list, set, delete

v3.94.0

Compare Source

Minor Changes

• #​7229 669d7ad Thanks @​gabivlj! - Introduce a new cloudchamber command wrangler cloudchamber apply, which will be used by customers to deploy container-apps

Patch Changes

• #​7002 d2447c6 Thanks @​GregBrimble! - fix: More helpful error messages when validating compatibility date

• #​7493 4c140bc Thanks @​emily-shen! - fix: remove non-json output in json mode commands

  Fixes regressions in 3.93.0 where unwanted text (wrangler banner, telemetry notice) was printing in commands that should only output valid json.

• Updated dependencies [5449fe5]:

  • @​cloudflare/workers-shared@​0.11.0
  • miniflare@3.20241205.0

---

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 was generated by Mend Renovate. View the repository job log.