Wrangler Changelog

​​ 2024-06-10

​​ 3.60.1

• #6002 Open external link f1f1834 Open external link Thanks @GregBrimble Open external link ! - Revert a change in 3.60.0 which incorrectly batched assets for Pages uploads ( https://github.com/cloudflare/workers-sdk/pull/5632 Open external link ).

​​ 2024-06-07

​​ 3.60.0

• #5878 Open external link 1e68fe5 Open external link Thanks @IgorMinar Open external link ! - feat: add experimental support for hybrid Node.js compatibility

  This feature is experimental and not yet available for general consumption.

  Use a combination of workerd Node.js builtins (behind the experimental:nodejs_compat_v2 flag) and Unenv polyfills (configured to only add those missing from the runtime) to provide a new more effective Node.js compatibility approach.

• #5988 Open external link e144f63 Open external link Thanks @RamIdeas Open external link ! - feature: rename the wrangler secret:bulk command to wrangler secret bulk

  The old command is now deprecated (but still functional) and will be removed in a future release. The new command is now more consistent with the rest of the wrangler CLI commands.

• #5989 Open external link 35b1a2f Open external link Thanks @RamIdeas Open external link ! - feature: rename wrangler kv:... commands to wrangler kv ...

  The old commands are now deprecated (but still functional) and will be removed in a future release. The new commands are now more consistent with the rest of the wrangler CLI commands.

• #5861 Open external link 1cc52f1 Open external link Thanks @zebp Open external link ! - feat: allow for Pages projects to upload sourcemaps

  Pages projects can now upload sourcemaps for server bundles to enable remapped stacktraces in realtime logs when deployed with upload_source_map set to true in wrangler.toml.

• #5939 Open external link 21573f4 Open external link Thanks @penalosa Open external link ! - refactor: Adds the experimental flag --x-dev-env which opts in to using an experimental code path for wrangler dev and wrangler dev --remote. There should be no observable behaviour changes when this flag is enabled.

• #5934 Open external link bac79fb Open external link Thanks @dbenCF Open external link ! - fix: Update create KV namespace binding details message for easier implementation

• #5927 Open external link 6f83641 Open external link Thanks @CarmenPopoviciu Open external link ! - fix: Clean pages dev terminal ouput

  This work includes a series of improvements to the pages dev terminal output, in an attempt to make this output more structured, organised, cleaner, easier to follow, and therefore more helpful for our users <3

• #5960 Open external link e648825 Open external link Thanks @petebacondarwin Open external link ! - fix: avoid injecting esbuild watch stubs into production Worker code

  When we added the ability to include additional modules in the deployed bundle of a Worker, we inadvertently also included some boiler plate code that is only needed at development time.

  This fix ensures that this code is only injected if we are running esbuild in watch mode (e.g. wrangler dev) and not when building for deployment.

  It is interesting to note that this boilerplate only gets included in the production code if there is an import of CommonJS code in the Worker, which esbuild needs to convert to an ESM import.

  Fixes #4269 Open external link

• Updated dependencies [ ab95473 Open external link ]:

  • miniflare@3.20240605.0

​​ 2024-06-04

​​ 3.59.0

• #5963 Open external link bf803d7 Open external link Thanks @Skye-31 Open external link ! - Feature: Add support for hiding the "unsafe" fields are experimental warning using an environment variable

  By setting WRANGLER_DISABLE_EXPERIMENTAL_WARNING to any truthy value, these warnings will be hidden.

• Updated dependencies [ bdbb7f8 Open external link ]:

  • miniflare@3.20240524.2

​​ 2024-05-31

​​ 3.58.0

• #5933 Open external link 93b98cb Open external link Thanks @WalshyDev Open external link ! - feature: allow for writing authentication details per API environment. This allows someone targetting staging to have their staging auth details saved separately from production, this saves them logging in and out when switching environments.

• #5938 Open external link 9e4d8bc Open external link Thanks @threepointone Open external link ! - fix: let “assets” in wrangler.toml be a string

  The experimental “assets” field can be either a string or an object. However the type definition marks it only as an object. This is a problem because we use this to generate the json schema, which gets picked up by vscode’s even better toml extension, and shows it to be an error when used with a string (even though it works fine). The fix is to simply change the type definition to add a string variant.

• #5758 Open external link 8e5e589 Open external link Thanks @Jackenmen Open external link ! - fix: use correct type for AI binding instead of unknown

• Updated dependencies [ e0e7725 Open external link ]:

  • miniflare@3.20240524.1

​​ 2024-05-28

​​ 3.57.2

• #5905 Open external link 53f22a0 Open external link Thanks @penalosa Open external link ! - fix: Remove WARP certificate injection. Instead, you should ensure that any custom certificates that are needed are included in NODE_EXTRA_CA_CERTS.

• #5930 Open external link 57daae0 Open external link Thanks @WalshyDev Open external link ! - chore: improve error message when updating secret for a non-deployed latest version.

• #5703 Open external link a905f31 Open external link Thanks @penalosa Open external link ! - fix: Don’t use ExportedHandler["middleware"] for injecting middleware

• Updated dependencies [ 64ccdd6 Open external link , 4458a9e Open external link ]:

  • miniflare@3.20240524.0

​​ 2024-05-21

​​ 3.57.1

• #5859 Open external link f2ceb3a Open external link Thanks @w-kuhn Open external link ! - fix: queue consumer max_batch_timeout should accept a 0 value

• #5862 Open external link 441a05f Open external link Thanks @CarmenPopoviciu Open external link ! - fix: wrangler pages deploy should fail if deployment was unsuccessful

  If a Pages project fails to deploy, wrangler pages deploy will log an error message, but exit successfully. It should instead throw a FatalError.

• #5812 Open external link d5e00e4 Open external link Thanks @thomasgauvin Open external link ! - fix: remove Hyperdrive warning for local development.

  Hyperdrive bindings are now supported when developing locally with Hyperdrive. We should update our logs to reflect this.

• #5626 Open external link a12b031 Open external link Thanks @RamIdeas Open external link ! - chore: ignore workerd output (error: CODE_MOVED) not intended for end-user devs

​​ 2024-05-17

​​ 3.57.0

• #5696 Open external link 7e97ba8 Open external link Thanks @geelen Open external link ! - feature: Improved d1 execute --file --remote performance & added support for much larger SQL files within a single transaction.

• #5819 Open external link 63f7acb Open external link Thanks @CarmenPopoviciu Open external link ! - fix: Show feedback on Pages project deployment failure

  Today, if uploading a Pages Function, or deploying a Pages project fails for whatever reason, there’s no feedback shown to the user. Worse yet, the shown message is misleading, saying the deployment was successful, when in fact it was not:

  ✨ Deployment complete!
  

  This commit ensures that we provide users with:

  • the correct feedback with respect to their Pages deployment
  • the appropriate messaging depending on the status of their project’s deployment status
  • the appropriate logs in case of a deployment failure

• #5814 Open external link 2869e03 Open external link Thanks @CarmenPopoviciu Open external link ! - fix: Display correct global flags in wrangler pages --help

  Running wrangler pages --help will list, amongst others, the following global flags:

  -j, --experimental-json-config
  -c, --config
  -e, --env
  -h, --help
  -v, --version
  

  This is not accurate, since flags such as --config, --experimental-json-config, or env are not supported by Pages.

  This commit ensures we display the correct global flags that apply to Pages.

• #5818 Open external link df2daf2 Open external link Thanks @WalshyDev Open external link ! - chore: Deprecate usage of the deployment object on the unsafe metadata binding in favor of the new version_metadata binding.

  If you’re currently using the old binding, please move over to the new version_metadata binding by adding:

  [version_metadata]
  binding = "CF_VERSION_METADATA"
  

  and updating your usage accordingly. You can find the docs for the new binding here: https://developers.cloudflare.com/workers/runtime-apis/bindings/version-metadata

• #5838 Open external link 609debd Open external link Thanks @petebacondarwin Open external link ! - fix: update undici to the latest version to avoid a potential vulnerability

• #5832 Open external link 86a6e09 Open external link Thanks @petebacondarwin Open external link ! - fix: do not allow non-string values in bulk secret uploads

  Prior to Wrangler 3.4.0 we displayed an error if the user tried to upload a JSON file that contained non-string secrets, since these are not supported by the Cloudflare backend.

  This change reintroduces that check to give the user a helpful error message rather than a cryptic workers.api.error.invalid_script_config error code.