cloudflare/workers-sdk wrangler@2.2.0

on GitHub

Minor Changes

• #2107 511943e9 Thanks @celso! - fix: D1 execute and backup commands improvements

  • Better and faster handling when importing big SQL files using execute --file
  • Increased visibility during imports, sends output with each batch API call
  • Backups are now downloaded to the directory where wrangler was initiated from

• #2130 68f4fa6f Thanks @matthewdavidrodgers! - feature: Add warnings around bundle sizes for large scripts

  Prints a warning for scripts > 1MB compressed, encouraging smaller
  script sizes. This warning can be silenced by setting the
  NO_SCRIPT_SIZE_WARNING env variable

  If a publish fails with either a script size error or a validator error
  on script startup (CPU or memory), we print out the largest 5
  dependencies in your bundle. This is accomplished by using the esbuild
  generated metafile.

• #2064 49b6a484 Thanks @jbw1991! - Adds support for Cloudflare Queues. Adds new CLI commands to configure Queues. Queue producers and consumers can be defined in wrangler.toml.

• #1982 5640fe88 Thanks @penalosa! - Enable support for wrangler dev on Workers behind Cloudflare Access, utilising cloudflared. If you don't have cloudflared installed, Wrangler will prompt you to install it. If you do, then the first time you start developing using wrangler dev your default browser will open with a Cloudflare Access prompt.

Patch Changes

• #2134 b164e2d6 Thanks @jspspike! - Added current version to publish output

• #2127 0e561e83 Thanks @JacobMGEvans! - Fix: Missing Worker name using --from-dash
  Added the --from-dash name as a fallback when no name is provided in the wrangler init command.
  Additionally added a checks to the std.out to ensure that the name is provided.

  resolves #1853

• #2073 1987a79d Thanks @mrbbot! - If --env <env> is specified, we'll now check .env.<env>/.dev.vars.<env> first.
  If they don't exist, we'll fallback to .env/.dev.vars.

• #2072 06aa6121 Thanks @mrbbot! - Fixed importing installed npm packages with the same name as Node built-in
  modules if node_compat is disabled.

• #2124 02ca556c Thanks @JacobMGEvans! - Computing the name from binding response
  Now the vars will be computed, example:
  [var.binding.name]: var.binding.text

  this will resolve the issue that was occurring with
  generating a TOML with incorrect fields for the vars key/value pair.

  resolves #2048