Bump wrangler from 3.13.1 to 3.21.0

[dependabot]

Bumps wrangler from 3.13.1 to 3.21.0.

Release notes

Sourced from wrangler's releases.

[email protected]

Minor Changes

• #4423 a94ef570 Thanks @​mrbbot! - feat: apply source mapping to logged strings

  Previously, Wrangler would only apply source mapping to uncaught exceptions. This meant if you caught an exception and logged its stack trace, the call sites would reference built JavaScript files as opposed to source files. This change looks for stack traces in logged messages, and tries to source map them.

  Note source mapping is only applied when outputting logs. Error#stack does not return a source mapped stack trace. This means the actual runtime value of new Error().stack and the output from console.log(new Error().stack) may be different.

Patch Changes

• #4511 66394681 Thanks @​huw! - Add 'took recursive isolate lock' warning to workerd output exceptions

[email protected]

Minor Changes

• #4522 c10bf0fd Thanks @​G4brym! - Add support for Workers AI in local mode

• #4571 3314dbde Thanks @​penalosa! - feat: When Wrangler crashes, send an error report to Sentry to aid in debugging.

  When Wrangler's top-level exception handler catches an error thrown from Wrangler's application, it will offer to report the error to Sentry. This requires opt-in from the user every time.

Patch Changes

• #4577 4c85fe99 Thanks @​dario-piotrowicz! - During the R2 validation, show MAX_UPLOAD_SIZE errors using MiB (consistently with the Cloudflare docs)

• #4577 4c85fe99 Thanks @​dario-piotrowicz! - During the Pages validation, show MAX_UPLOAD_SIZE errors using MiB (consistently with the Cloudflare docs)

• Updated dependencies [eb08e2dc]:

  • [email protected]

[email protected]

Minor Changes

• #4547 86c81ff0 Thanks @​mrbbot! - fix: listen on IPv4 loopback only by default on Windows

  Due to a known issue, workerd will only listen on the IPv4 loopback address 127.0.0.1 when it's asked to listen on localhost. On Node.js > 17, localhost will resolve to the IPv6 loopback address, meaning requests to workerd would fail. This change switches to using the IPv4 loopback address throughout Wrangler on Windows, while workerd#1408 gets fixed.

• #4535 29df8e17 Thanks @​mrbbot! - Reintroduces some internal refactorings of wrangler dev servers (including wrangler dev, wrangler dev --remote, and unstable_dev()).

  These changes were released in 3.13.0 and reverted in 3.13.1 -- we believe the changes are now more stable and ready for release again.

  There are no changes required for developers to opt-in. Improvements include:

  • fewer 'address in use' errors upon reloads
  • upon config/source file changes, requests are buffered to guarantee the response is from the new version of the Worker

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.21.0

Minor Changes

• #4423 a94ef570 Thanks @​mrbbot! - feat: apply source mapping to logged strings

  Previously, Wrangler would only apply source mapping to uncaught exceptions. This meant if you caught an exception and logged its stack trace, the call sites would reference built JavaScript files as opposed to source files. This change looks for stack traces in logged messages, and tries to source map them.

  Note source mapping is only applied when outputting logs. Error#stack does not return a source mapped stack trace. This means the actual runtime value of new Error().stack and the output from console.log(new Error().stack) may be different.

Patch Changes

• #4511 66394681 Thanks @​huw! - Add 'took recursive isolate lock' warning to workerd output exceptions

3.20.0

Minor Changes

• #4522 c10bf0fd Thanks @​G4brym! - Add support for Workers AI in local mode

• #4571 3314dbde Thanks @​penalosa! - feat: When Wrangler crashes, send an error report to Sentry to aid in debugging.

  When Wrangler's top-level exception handler catches an error thrown from Wrangler's application, it will offer to report the error to Sentry. This requires opt-in from the user every time.

Patch Changes

• #4577 4c85fe99 Thanks @​dario-piotrowicz! - During the R2 validation, show MAX_UPLOAD_SIZE errors using MiB (consistently with the Cloudflare docs)

• #4577 4c85fe99 Thanks @​dario-piotrowicz! - During the Pages validation, show MAX_UPLOAD_SIZE errors using MiB (consistently with the Cloudflare docs)

• Updated dependencies [eb08e2dc]:

  • [email protected]

3.19.0

Minor Changes

• #4547 86c81ff0 Thanks @​mrbbot! - fix: listen on IPv4 loopback only by default on Windows

  Due to a known issue, workerd will only listen on the IPv4 loopback address 127.0.0.1 when it's asked to listen on localhost. On Node.js > 17, localhost will resolve to the IPv6 loopback address, meaning requests to workerd would fail. This change switches to using the IPv4 loopback address throughout Wrangler on Windows, while workerd#1408 gets fixed.

• #4535 29df8e17 Thanks @​mrbbot! - Reintroduces some internal refactorings of wrangler dev servers (including wrangler dev, wrangler dev --remote, and unstable_dev()).

  These changes were released in 3.13.0 and reverted in 3.13.1 -- we believe the changes are now more stable and ready for release again.

  There are no changes required for developers to opt-in. Improvements include:

  • fewer 'address in use' errors upon reloads
  • upon config/source file changes, requests are buffered to guarantee the response is from the new version of the Worker

... (truncated)

Commits

• 912bfeb Version Packages (#4595)
• a94ef57 [wrangler] feat: source map logged strings (#4423)
• 6639468 Add took recursive isolate lock warning to workerd output exceptions (#4511)
• 7506b24 Version Packages (#4559)
• 6722468 Various --from-dash improvements (#4470)
• ba9b88f Add workers ai usage warning in local mode (#4586)
• 3314dbd Send Crash Reports to Sentry (#4571)
• 609430b update link to template directory for wrangler -h (#3724)
• 4c85fe9 During Pages and R2 validations, show sizes in MiB (consistently with the Clo...
• c10bf0f Add support for Workers AI in local mode (#4522)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #253.