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)

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)

• 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

Sourced from wrangler's releases.

wrangler@4.25.1

Patch Changes

• #10000 c02b067 Thanks @​emily-shen! - Include more (sanitised) user errors in telemetry.

  We manually vet and sanitised error messages before including them in our telemetry collection - this PR just includes a couple more.

• #9996 b0217f9 Thanks @​nikitassharma! - Disallow users from pushing images with unsupported platforms to the container image registry

• #10009 e87198a Thanks @​gpanders! - Fix containers diff output when using JSONC config files

• #9976 ad02ad3 Thanks @​dario-piotrowicz! - add warning for when users run wrangler dev --remote with (enabled) containers

• #9819 0c4008c Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add containers support in vite dev

  Adds support for Cloudflare Containers in vite dev. Please note that at the time of this PR a container image can only specify the path to a Dockerfile. Support for registry links will be added in a later version, as will containers support in vite preview.

• Updated dependencies [189fe23, 7e5585d]:

  • @​cloudflare/unenv-preset@​2.4.0
  • miniflare@4.20250712.1

wrangler@4.25.0

Minor Changes

• #9835 9f0c175 Thanks @​thomasgauvin! - Added rename namespace command to Workers KV

Patch Changes

• #9934 6cc24c0 Thanks @​emily-shen! - Add more thorough validation to containers configuration

wrangler@4.24.4

Patch Changes

• #9905 4ba9f25 Thanks @​dom96! - Support for Python packages in python_modules dir

• #9886 17b1e5a Thanks @​dom96! - Python packages are now read from cf-requirements.txt instead of requirements.txt by default

• #9899 d6a1b9b Thanks @​simonabadoiu! - Print local mode when running a browser binding in local mode

• #9951 e2672c5 Thanks @​penalosa! - Recommend remote bindings when wrangler dev --remote is used

• #9875 a5d7b35 Thanks @​gpanders! - Show expected format in error message for "containers images delete"

• #9954 bf4c9ab Thanks @​penalosa! - Support Images binding in getPlatformProxy()

• #9847 14ce577 Thanks @​penalosa! - Upgrade Undici

• #9974 f73da0d Thanks @​penalosa! - Pass worker name & compliance region through correctly when starting a remote bindings session

• Updated dependencies [ac08e68, 3bb69fa, 274a826, 77d1cb2, 5b0fc9e, bf4c9ab, 14ce577]:

... (truncated)

Sourced from wrangler's changelog.

4.25.1

Patch Changes

• #10000 c02b067 Thanks @​emily-shen! - Include more (sanitised) user errors in telemetry.

  We manually vet and sanitised error messages before including them in our telemetry collection - this PR just includes a couple more.

• #9996 b0217f9 Thanks @​nikitassharma! - Disallow users from pushing images with unsupported platforms to the container image registry

• #10009 e87198a Thanks @​gpanders! - Fix containers diff output when using JSONC config files

• #9976 ad02ad3 Thanks @​dario-piotrowicz! - add warning for when users run wrangler dev --remote with (enabled) containers

• #9819 0c4008c Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add containers support in vite dev

  Adds support for Cloudflare Containers in vite dev. Please note that at the time of this PR a container image can only specify the path to a Dockerfile. Support for registry links will be added in a later version, as will containers support in vite preview.

• Updated dependencies [189fe23, 7e5585d]:

  • @​cloudflare/unenv-preset@​2.4.0
  • miniflare@4.20250712.1

4.25.0

Minor Changes

• #9835 9f0c175 Thanks @​thomasgauvin! - Added rename namespace command to Workers KV

Patch Changes

• #9934 6cc24c0 Thanks @​emily-shen! - Add more thorough validation to containers configuration

4.24.4

Patch Changes

• #9905 4ba9f25 Thanks @​dom96! - Support for Python packages in python_modules dir

• #9886 17b1e5a Thanks @​dom96! - Python packages are now read from cf-requirements.txt instead of requirements.txt by default

• #9899 d6a1b9b Thanks @​simonabadoiu! - Print local mode when running a browser binding in local mode

• #9951 e2672c5 Thanks @​penalosa! - Recommend remote bindings when wrangler dev --remote is used

• #9875 a5d7b35 Thanks @​gpanders! - Show expected format in error message for "containers images delete"

• #9954 bf4c9ab Thanks @​penalosa! - Support Images binding in getPlatformProxy()

• #9847 14ce577 Thanks @​penalosa! - Upgrade Undici

... (truncated)

• 7d14000 Version Packages (#10002)
• a355327 Resolve dockerfile to absolute path in redirected config in vite plugin (#10038)
• 08b37f8 Revert "use userConfigPath instead of redirected one (#10005)" (#10037)
• 64d71b1 use userConfigPath instead of redirected one (#10005)
• 0c4008c feat(vite-plugin): Add containers support in vite-plugin (#9819)
• e87198a Fix container diffs when using JSONC config (#10009)
• b0217f9 Require container images use a supported platform (#9996)
• 89cb004 refactor asynchronous code (#10017)
• f7f97de cleanup: remove dead code (#10011)
• 7e5585d fix: escape column names and handle mismatched data types in D1 SQL dump (#9866)
• Additional commits viewable in compare view

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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.