cloudflare/workers-sdk wrangler@2.1.12

on GitHub

Patch Changes

• #2023 d6660ce3 Thanks @caass! - Display a more helpful error when trying to publish to a route in use by another worker.

  Previously, when trying to publish a worker to a route that was in use by another worker,
  there would be a really unhelpful message about a failed API call. Now, there's a much
  nicer message that tells you what worker is running on that route, and gives you a link
  to the workers overview page so you can unassign it if you want.

   ⛅️ wrangler 2.1.11
  --------------------
  Total Upload: 0.20 KiB / gzip: 0.17 KiB
  
  ✘ [ERROR] Can't publish a worker to routes that are assigned to another worker.
  
    "test-custom-routes-redeploy" is already assigned to route
    test-custom-worker.swag.lgbt
  
    Unassign other workers from the routes you want to publish to, and then try again.
    Visit
    https://dash.cloudflare.com/<account_id>/workers/overview
    to unassign a worker from a route.
  

  Closes #1849

• #2013 c63ca0a5 Thanks @rozenmd! - fix: make d1 help print if a command is incomplete

  Prior to this change, d1's commands would return silently if wrangler wasn't supplied enough arguments to run the command.

  This change resolves this issue, and ensures help is always printed if the command couldn't run.

• #2016 932fecc0 Thanks @caass! - Offer to create a workers.dev subdomain if a user needs one

  Previously, when a user wanted to publish a worker to https://workers.dev by setting workers_dev = true in their wrangler.toml,
  but their account didn't have a subdomain registered, we would error out.

  Now, we offer to create one for them. It's not implemented for wrangler dev, which also expects you to have registered a
  workers.dev subdomain, but we now error correctly and tell them what the problem is.

• #2003 3ed06b40 Thanks @GregBrimble! - chore: Bump miniflare@2.10.0

• #2024 4ad48e4d Thanks @rozenmd! - fix: make it possible for values in vars and defines to have colons (:)

  Prior to this change, passing --define someKey:https://some-value.com would result in an incomplete value being passed to the Worker.

  This change correctly handles colons for var and define in wrangler dev and wrangler publish.

• #2032 f33805d2 Thanks @caass! - Catch unsupported terminal errors and provide a nicer error message.

  Wrangler depends on terminals supporting raw mode. Previously, attempting to run wrangler from a terminal that didn't support raw mode would result in
  an Ink error, which was both an exposure of an internal implementation detail to the user and also not actionable:

    ERROR Raw mode is not supported on the current process.stdin, which Ink uses
         as input stream by default.
         Read about how to prevent this error on
         https://github.com/vadimdemedes/ink/#israwmodesupported
  

  Now, we provide a much nicer error, which provides an easy next step for th user:

  
  ERROR: This terminal doesn't support raw mode.
  
  Wrangler uses raw mode to read user input and write output to the terminal, and won't function correctly without it.
  
  Try running your previous command in a terminal that supports raw mode, such as Command Prompt or Powershell.
  

  Closes #1992

• #1946 7716c3b9 Thanks @penalosa! - Support subdomains with wrangler dev for routes defined with zone_name (instead of just for routes defined with zone_id)