cloudflare/workers-sdk wrangler@2.0.26

on GitHub

Patch Changes

• #1655 fed80faa Thanks @jahands! - fix: Pages Functions custom _routes.json not being used

  Also cleaned up when we were reading generated _routes.json

• #1649 a366b12f Thanks @Skye-31! - fix: [windows] unable to find netstat

• #1626 f650a0b2 Thanks @JacobMGEvans! - fix: Added pathname to the constructed URL service bindings + wrangler dev ignores pathname when making a request.

  resolves #1598

• #1648 af669a19 Thanks @CarmenPopoviciu! - Implement new wrangler pages functions optimize-routes command

• #1622 02bdfde0 Thanks @Skye-31! - fix: Handle static files with multiple extensions, e.g. /a.b should resolve /a.b.html, if /a.b as a file does not exist

• #1666 662dfdf9 Thanks @jahands! - fix: Consolidate routes that are over the limit to prevent failed deployments

  Rather than failing a deployment because a route is too long (>100 characters), it will now be shortened to the next available level. Eg.
  /foo/aaaaaaa... -> /foo/*

#1670 1b232aaf Thanks @Skye-31! - fix: dev.tsx opens 127.0.0.1 instead of 0.0.0.0 (doesn't work on windows)

• #1671 808c0ab3 Thanks @Skye-31! - feat: pages publish - log special files being uploaded

• #1656 37852672 Thanks @jahands! - fix: Warn when Pages Functions have no routes

  Building/publishing pages functions with no valid handlers would result in a Functions script containing no routes, often because the
  user is using the functions directory for something unrelated. This will no longer add an empty Functions script to the deployment,
  needlessly consuming Functions quota.

• #1665 c40fca42 Thanks @GregBrimble! - fix: Fix SW and Durable Object request URLs made over the service registry

• #1645 ac397480 Thanks @JacobMGEvans! - feat: download & initialize a wrangler project from dashboard worker

  Added wrangler init --from-dash , which allows initializing a wrangler project from a pre-existing worker in the
  dashboard.

  Resolves #1624 Discussion: #1623

  Notes: multiplart/form-data parsing is nodejs/undici#974, so a temporary workaround to slice off top and
  bottom boundaries is in place.

• #1639 d86382a5 Thanks @matthewdavidrodgers! - fix: support 'exceededMemory' error status in tail

  While the exception for 'Worker exceeded memory limits' gets logged correctly when tailing, the actual status wasn't being counted as
  an error, and was falling through a switch case to 'unknown'

  This ensures filtering and logging reflects that status correctly