Bump esbuild and wrangler in /worker

[dependabot]

Bumps esbuild to 0.25.4 and updates ancestor dependency wrangler. These dependencies need to be updated together.

Updates esbuild from 0.17.19 to 0.25.4

Release notes

Sourced from esbuild's releases.

v0.25.4

• Add simple support for CORS to esbuild's development server (#4125)

  Starting with version 0.25.0, esbuild's development server is no longer configured to serve cross-origin requests. This was a deliberate change to prevent any website you visit from accessing your running esbuild development server. However, this change prevented (by design) certain use cases such as "debugging in production" by having your production website load code from localhost where the esbuild development server is running.

  To enable this use case, esbuild is adding a feature to allow Cross-Origin Resource Sharing (a.k.a. CORS) for simple requests. Specifically, passing your origin to the new cors option will now set the Access-Control-Allow-Origin response header when the request has a matching Origin header. Note that this currently only works for requests that don't send a preflight OPTIONS request, as esbuild's development server doesn't currently support OPTIONS requests.

  Some examples:

  • CLI:

    esbuild --servedir=. --cors-origin=https://example.com
    

  • JS:

    const ctx = await esbuild.context({})
    await ctx.serve({
      servedir: '.',
      cors: {
        origin: 'https://example.com',
      },
    })

  • Go:

    ctx, _ := api.Context(api.BuildOptions{})
    ctx.Serve(api.ServeOptions{
      Servedir: ".",
      CORS: api.CORSOptions{
        Origin: []string{"https://example.com"},
      },
    })

  The special origin * can be used to allow any origin to access esbuild's development server. Note that this means any website you visit will be able to read everything served by esbuild.

• Pass through invalid URLs in source maps unmodified (#4169)

  This fixes a regression in version 0.25.0 where sources in source maps that form invalid URLs were not being passed through to the output. Version 0.25.0 changed the interpretation of sources from file paths to URLs, which means that URL parsing can now fail. Previously URLs that couldn't be parsed were replaced with the empty string. With this release, invalid URLs in sources should now be passed through unmodified.

• Handle exports named __proto__ in ES modules (#4162, #4163)

  In JavaScript, the special property name __proto__ sets the prototype when used inside an object literal. Previously esbuild's ESM-to-CommonJS conversion didn't special-case the property name of exports named __proto__ so the exported getter accidentally became the prototype of the object literal. It's unclear what this affects, if anything, but it's better practice to avoid this by using a computed property name in this case.

  This fix was contributed by @​magic-akari.

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

• Fix TypeScript-specific class transform edge case (#3559)

  The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

  // Original code
  class Foo extends Bar {
    #private = 1;
    public: any;
    constructor() {
      super();
    }
  }
  // Old output (with esbuild v0.19.9)
  class Foo extends Bar {
  constructor() {
  super();
  this.#private = 1;
  }
  #private;
  }
  // Old output (with esbuild v0.19.10)
  class Foo extends Bar {
  constructor() {
  this.#private = 1;
  super();
  }
  #private;
  }
  // New output
  class Foo extends Bar {
  #private = 1;
  constructor() {
  super();
  }
  }

• Minifier: allow reording a primitive past a side-effect (#3568)

  The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits

• 218d29e publish 0.25.4 to npm
• e66cd0b dev server: simple support for CORS requests (#4171)
• 8bf3368 js api: validate some options as arrays of strings
• 1e7375a js api: simplify comma-separated array validation
• 5f5964d release notes for #4163
• adb5284 fix: handle __proto__ as a computed property in exports and add tests for s...
• 0aa9f7b fix #4169: keep invalid source map URLs unmodified
• 5959289 add additional guards for #4114 when using :is()
• 677910b publish 0.25.3 to npm
• a41040e fix #4110: support custom non-IP host values
• Additional commits viewable in compare view

Updates wrangler from 3.114.9 to 4.20.3

Release notes

Sourced from wrangler's releases.

wrangler@4.20.3

Patch Changes

• #9621 08be3ed Thanks @​gabivlj! - wrangler containers: 'default' scheduling policy should be the default

• #9586 d1d34fe Thanks @​penalosa! - Remove the Mixed Mode naming in favour of "remote bindings"/"remote proxy"

• Updated dependencies [d1d34fe]:

  • miniflare@4.20250617.1

wrangler@4.20.2

Patch Changes

• #9565 b1c9139 Thanks @​IRCody! - Ensure that a container applications image configuration is not updated if there were not changes to the image.

• #9628 92f12f4 Thanks @​gpanders! - Remove "Cloudchamber" from user facing error messages

• #9576 2671e77 Thanks @​vicb! - Add core local dev functionality for containers. Adds a new WRANGLER_DOCKER_HOST env var to customise what socket to connect to.

• Updated dependencies [828b7df, 2671e77]:

  • miniflare@4.20250617.0

wrangler@4.20.1

Patch Changes

• #9536 3b61c41 Thanks @​dario-piotrowicz! - expose Unstable_Binding type

• #9564 1d3293f Thanks @​skepticfx! - Switch container registry to registry.cloudflare.com from registry.cloudchamber.cfdata.org. Also adds the env var CLOUDFLARE_CONTAINER_REGISTRY to override this

• #9520 04f9164 Thanks @​vicb! - fix the default value for keep_names (true)

• #9506 36113c2 Thanks @​penalosa! - Strip the CF-Connecting-IP header from outgoing fetches

• #9592 49f5ac7 Thanks @​petebacondarwin! - Point to the right location for docs on telemetry

• #9593 cf33417 Thanks @​vicb! - drop unused WRANGLER_UNENV_RESOLVE_PATHS env var

• #9566 521eeb9 Thanks @​vicb! - Bump @cloudflare/unenv-preset to 2.3.3

• #9344 02e2c1e Thanks @​dario-piotrowicz! - add warning about env not specified to potentially risky wrangler commands

  add a warning suggesting users to specify their target environment (via -e or --env) when their wrangler config file contains some environments and they are calling one of the following commands:

  • wrangler deploy
  • wrangler versions upload
  • wrangler versions deploy

... (truncated)

Changelog

Sourced from wrangler's changelog.

4.20.3

Patch Changes

• #9621 08be3ed Thanks @​gabivlj! - wrangler containers: 'default' scheduling policy should be the default

• #9586 d1d34fe Thanks @​penalosa! - Remove the Mixed Mode naming in favour of "remote bindings"/"remote proxy"

• Updated dependencies [d1d34fe]:

  • miniflare@4.20250617.1

4.20.2

Patch Changes

• #9565 b1c9139 Thanks @​IRCody! - Ensure that a container applications image configuration is not updated if there were not changes to the image.

• #9628 92f12f4 Thanks @​gpanders! - Remove "Cloudchamber" from user facing error messages

• #9576 2671e77 Thanks @​vicb! - Add core local dev functionality for containers. Adds a new WRANGLER_DOCKER_HOST env var to customise what socket to connect to.

• Updated dependencies [828b7df, 2671e77]:

  • miniflare@4.20250617.0

4.20.1

Patch Changes

• #9536 3b61c41 Thanks @​dario-piotrowicz! - expose Unstable_Binding type

• #9564 1d3293f Thanks @​skepticfx! - Switch container registry to registry.cloudflare.com from registry.cloudchamber.cfdata.org. Also adds the env var CLOUDFLARE_CONTAINER_REGISTRY to override this

• #9520 04f9164 Thanks @​vicb! - fix the default value for keep_names (true)

• #9506 36113c2 Thanks @​penalosa! - Strip the CF-Connecting-IP header from outgoing fetches

• #9592 49f5ac7 Thanks @​petebacondarwin! - Point to the right location for docs on telemetry

• #9593 cf33417 Thanks @​vicb! - drop unused WRANGLER_UNENV_RESOLVE_PATHS env var

• #9566 521eeb9 Thanks @​vicb! - Bump @cloudflare/unenv-preset to 2.3.3

• #9344 02e2c1e Thanks @​dario-piotrowicz! - add warning about env not specified to potentially risky wrangler commands

  add a warning suggesting users to specify their target environment (via -e or --env) when their wrangler config file contains some environments and they are calling one of the following commands:

  • wrangler deploy

... (truncated)

Commits

• 225b8bf Version Packages (#9650)
• 08be3ed containers: Default scheduling policy should be the default (#9621)
• d1d34fe Rename Mixed Mode to remote proxy/remote bindings depending on context (#9586)
• 9fd3e5f Version Packages (#9632)
• 8e6bf09 Correctly mock out getDockerImageDigest for testing buildAndMaybePush (#9636)
• 92f12f4 Remove "Cloudchamber" from user facing error messages (#9628)
• 2671e77 sync local containers with latest workerd (#9576)
• 828b7df Bump the workerd-and-workers-types group with 2 updates (#9591)
• 692f3d7 remote unnecessary getStore line (#9615)
• b1c9139 Do not update container apps image if the image is unchanged (#9565)
• 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[cloudflare-workers-and-pages]

Deploying tatebayashistones with    Cloudflare Pages

Latest commit:	cee1abd
Status:	✅  Deploy successful!
Preview URL:	https://36a2e724.tatebayashistones.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-work.tatebayashistones.pages.dev

View logs