fix(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@cloudflare/workers-types	4.20250421.0 -> 4.20250424.0
aws-cdk (source)	2.1010.0 -> 2.1012.0
aws-cdk-lib (source)	2.190.0 -> 2.191.0
esbuild	0.25.2 -> 0.25.3
eslint (source)	9.25.0 -> 9.25.1
fast-xml-parser	5.2.0 -> 5.2.1
svelte (source)	5.28.1 -> 5.28.2
wrangler (source)	4.12.0 -> 4.13.0

---

Release Notes

cloudflare/workerd (@​cloudflare/workers-types)

v4.20250424.0

Compare Source

v4.20250423.0

Compare Source

v4.20250422.0

Compare Source

aws/aws-cdk-cli (aws-cdk)

v2.1012.0

Compare Source

2.1012.0 (2025-04-23)

Features

• toolkit-lib: make base credentials configurable (#​388) (7c3c94e)
• toolkit-lib: make the plugin host configurable (#​375) (4c3aaa8)

Bug Fixes

• cli: remove unnecessary dom lib from default TypeScript config created with cdk init (#​295) (65f7015), closes #​294

v2.1011.0

Compare Source

2.1011.0 (2025-04-23)

Features

• toolkit-lib: make base credentials configurable (#​388) (7c3c94e)
• toolkit-lib: make the plugin host configurable (#​375) (4c3aaa8)

Bug Fixes

• cli: remove unnecessary dom lib from default TypeScript config created with cdk init (#​295) (65f7015), closes #​294

aws/aws-cdk (aws-cdk-lib)

v2.191.0

Compare Source

⚠ BREAKING CHANGES TO EXPERIMENTAL FEATURES

• cloudformation: Some L1 resources experienced breaking changes due to
  updated CloudFormation resources. Please check the notes for each
  specific module for more information.
• neptune-alpha: Id attribute is being removed from the
  AWS::Neptune::DBClusterParameterGroup and AWS::Neptune::DBParameterGroup
  resources
• aws-launchwizard: specifications prop moved from required to
  optional in CfnDeployment
• aws-ses: attribute attribute moved from required to optional in
  RuleBooleanToEvaluateProperty

Features

• cloudformation: update L1 CloudFormation resource definitions (#​34207) (adfa416)
• update L1 CloudFormation resource definitions (e3483c2)
• codebuild: add additional build images for lambda (#​34197) (5a265d1)
• rds: add Aurora MySQL versions 2.12.4, 3.08.2 (#​34045) (1dd993e)

---

Alpha modules (2.191.0-alpha.0)

Features

• location: throw ValidationError instead of untyped errors (#​34174) (2ecf14a)
• msk: throw ValidationError instead of untyped errors (#​34214) (02cb5a4)

evanw/esbuild (esbuild)

v0.25.3

Compare Source

• Fix lowered async arrow functions before super() (#​4141, #​4142)

  This change makes it possible to call an async arrow function in a constructor before calling super() when targeting environments without async support, as long as the function body doesn't reference this. Here's an example (notice the change from this to null):

  // Original code
  class Foo extends Object {
    constructor() {
      (async () => await foo())()
      super()
    }
  }
  
  // Old output (with --target=es2016)
  class Foo extends Object {
    constructor() {
      (() => __async(this, null, function* () {
        return yield foo();
      }))();
      super();
    }
  }
  
  // New output (with --target=es2016)
  class Foo extends Object {
    constructor() {
      (() => __async(null, null, function* () {
        return yield foo();
      }))();
      super();
    }
  }

  Some background: Arrow functions with the async keyword are transformed into generator functions for older language targets such as --target=es2016. Since arrow functions capture this, the generated code forwards this into the body of the generator function. However, JavaScript class syntax forbids using this in a constructor before calling super(), and this forwarding was problematic since previously happened even when the function body doesn't use this. Starting with this release, esbuild will now only forward this if it's used within the function body.

  This fix was contributed by @​magic-akari.

• Fix memory leak with --watch=true (#​4131, #​4132)

  This release fixes a memory leak with esbuild when --watch=true is used instead of --watch. Previously using --watch=true caused esbuild to continue to use more and more memory for every rebuild, but --watch=true should now behave like --watch and not leak memory.

  This bug happened because esbuild disables the garbage collector when it's not run as a long-lived process for extra speed, but esbuild's checks for which arguments cause esbuild to be a long-lived process weren't updated for the new --watch=true style of boolean command-line flags. This has been an issue since this boolean flag syntax was added in version 0.14.24 in 2022. These checks are unfortunately separate from the regular argument parser because of how esbuild's internals are organized (the command-line interface is exposed as a separate Go API so you can build your own custom esbuild CLI).

  This fix was contributed by @​mxschmitt.

• More concise output for repeated legal comments (#​4139)

  Some libraries have many files and also use the same legal comment text in all files. Previously esbuild would copy each legal comment to the output file. Starting with this release, legal comments duplicated across separate files will now be grouped in the output file by unique comment content.

• Allow a custom host with the development server (#​4110)

  With this release, you can now use a custom non-IP host with esbuild's local development server (either with --serve= for the CLI or with the serve() call for the API). This was previously possible, but was intentionally broken in version 0.25.0 to fix a security issue. This change adds the functionality back except that it's now opt-in and only for a single domain name that you provide.

  For example, if you add a mapping in your /etc/hosts file from local.example.com to 127.0.0.1 and then use esbuild --serve=local.example.com:8000, you will now be able to visit http://local.example.com:8000/ in your browser and successfully connect to esbuild's development server (doing that would previously have been blocked by the browser). This should also work with HTTPS if it's enabled (see esbuild's documentation for how to do that).

• Add a limit to CSS nesting expansion (#​4114)

  With this release, esbuild will now fail with an error if there is too much CSS nesting expansion. This can happen when nested CSS is converted to CSS without nesting for older browsers as expanding CSS nesting is inherently exponential due to the resulting combinatorial explosion. The expansion limit is currently hard-coded and cannot be changed, but is extremely unlikely to trigger for real code. It exists to prevent esbuild from using too much time and/or memory. Here's an example:

  a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}

  Previously, transforming this file with --target=safari1 took 5 seconds and generated 40mb of CSS. Trying to do that will now generate the following error instead:

  ✘ [ERROR] CSS nesting is causing too much expansion
  
      example.css:1:60:
        1 │ a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}
          ╵                                                             ^
  
    CSS nesting expansion was terminated because a rule was generated with 65536 selectors. This limit
    exists to prevent esbuild from using too much time and/or memory. Please change your CSS to use
    fewer levels of nesting.
  

• Fix path resolution edge case (#​4144)

  This fixes an edge case where esbuild's path resolution algorithm could deviate from node's path resolution algorithm. It involves a confusing situation where a directory shares the same file name as a file (but without the file extension). See the linked issue for specific details. This appears to be a case where esbuild is correctly following node's published resolution algorithm but where node itself is doing something different. Specifically the step LOAD_AS_FILE appears to be skipped when the input ends with ... This release changes esbuild's behavior for this edge case to match node's behavior.

• Update Go from 1.23.7 to 1.23.8 (#​4133, #​4134)

  This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses, such as for CVE-2025-22871.

  As a reminder, esbuild's development server is intended for development, not for production, so I do not consider most networking-related vulnerabilities in Go to be vulnerabilities in esbuild. Please do not use esbuild's development server in production.

eslint/eslint (eslint)

v9.25.1

Compare Source

NaturalIntelligence/fast-xml-parser (fast-xml-parser)

v5.2.1

Compare Source

sveltejs/svelte (svelte)

v5.28.2

Compare Source

Patch Changes

• fix: don't mark selector lists inside :global with multiple items as unused (#​15817)

cloudflare/workers-sdk (wrangler)

v4.13.0

Compare Source

Minor Changes

• #​8640 5ce70bd Thanks @​kentonv! - Add support for defining props on a Service binding.

  In your configuration file, you can define a service binding with props:

  {
  	"services": [
  		{
  			"binding": "MY_SERVICE",
  			"service": "some-worker",
  			"props": { "foo": 123, "bar": "value" }
  		}
  	]
  }

  These can then be accessed by the callee:

  import { WorkerEntrypoint } from "cloudflare:workers";
  
  export default class extends WorkerEntrypoint {
  	fetch() {
  		return new Response(JSON.stringify(this.ctx.props));
  	}
  }

• #​8771 0cfcfe0 Thanks @​dario-piotrowicz! - feat: add config.keep_names option

  Adds a new option to Wrangler to allow developers to opt out of esbuild's keep_names option (https://esbuild.github.io/api/#keep-names). By default, Wrangler sets this to true

  This is something developers should not usually need to care about, but sometimes
  keep_names can create issues, and in such cases they will be now able to opt-out.

  Example wrangler.jsonc:

  {
  	"name": "my-worker",
  	"main": "src/worker.ts",
  	"keep_names": false
  }

Patch Changes

• #​9024 c409318 Thanks @​IRCody! - Correctly handle 0 length responses to wrangler containers list.

• Updated dependencies [5ce70bd, 3f0adf3]:

  • [email protected]

v4.12.1

Compare Source

Patch Changes

• #​8935 41f095b Thanks @​penalosa! - Internal refactor to move local analytics engine support from Wrangler to Miniflare

• Updated dependencies [2a7749b, 41f095b]:

  • [email protected]

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Apollo Federation Subgraph Compatibility Results

Federation 1 Support	Federation 2 Support
_service 🟢 @key (single) 🟢 @key (multi) 🟢 @key (composite) 🟢 repeatable @key 🟢 @requires 🟢 @provides 🟢 federated tracing 🟢	@link 🟢 @shareable 🟢 @tag 🟢 @override 🟢 @inaccessible 🟢 @composeDirective 🟢 @interfaceObject 🟢

Learn more:

• Apollo Federation Subgraph Specification
• Compatibility Tests

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://pr-4014.graphql-yoga.pages.dev

[github-actions]

✅ Benchmark Results

     ✓ no_errors{mode:graphql}
     ✓ expected_result{mode:graphql}
     ✓ no_errors{mode:graphql-jit}
     ✓ expected_result{mode:graphql-jit}
     ✓ no_errors{mode:graphql-response-cache}
     ✓ expected_result{mode:graphql-response-cache}
     ✓ no_errors{mode:graphql-no-parse-validate-cache}
     ✓ expected_result{mode:graphql-no-parse-validate-cache}
     ✓ no_errors{mode:uws}
     ✓ expected_result{mode:uws}

     checks.......................................: 100.00% ✓ 456806      ✗ 0     
     data_received................................: 1.8 GB  12 MB/s
     data_sent....................................: 92 MB   612 kB/s
     http_req_blocked.............................: avg=1.62µs   min=1.05µs   med=1.41µs   max=290.48µs p(90)=2.08µs   p(95)=2.26µs  
     http_req_connecting..........................: avg=2ns      min=0s       med=0s       max=152.17µs p(90)=0s       p(95)=0s      
     http_req_duration............................: avg=433.57µs min=295.73µs med=397µs    max=18.63ms  p(90)=559.03µs p(95)=582.56µs
       { expected_response:true }.................: avg=433.57µs min=295.73µs med=397µs    max=18.63ms  p(90)=559.03µs p(95)=582.56µs
     ✓ { mode:graphql-jit }.......................: avg=373.99µs min=297.12µs med=355.98µs max=18.63ms  p(90)=390.34µs p(95)=403.71µs
     ✓ { mode:graphql-no-parse-validate-cache }...: avg=583.28µs min=496.1µs  med=560.43µs max=5.82ms   p(90)=601.27µs p(95)=654.29µs
     ✓ { mode:graphql-response-cache }............: avg=430.22µs min=347.02µs med=412.57µs max=7.26ms   p(90)=446.8µs  p(95)=459.95µs
     ✓ { mode:graphql }...........................: avg=447.12µs min=353.85µs med=417.32µs max=17.69ms  p(90)=475µs    p(95)=524.61µs
     ✓ { mode:uws }...............................: avg=373.97µs min=295.73µs med=353.66µs max=6.01ms   p(90)=390.04µs p(95)=421.31µs
     http_req_failed..............................: 0.00%   ✓ 0           ✗ 228403
     http_req_receiving...........................: avg=33.53µs  min=16.6µs   med=32.71µs  max=3.46ms   p(90)=39.47µs  p(95)=42.06µs 
     http_req_sending.............................: avg=9.16µs   min=6.11µs   med=8.31µs   max=440.32µs p(90)=11.42µs  p(95)=12.89µs 
     http_req_tls_handshaking.....................: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting.............................: avg=390.87µs min=263.84µs med=355.32µs max=18.48ms  p(90)=515.99µs p(95)=538.35µs
     http_reqs....................................: 228403  1522.674295/s
     iteration_duration...........................: avg=651.6µs  min=477.11µs med=611.91µs max=19.18ms  p(90)=779.54µs p(95)=805.71µs
     iterations...................................: 228403  1522.674295/s
     vus..........................................: 1       min=1         max=1   
     vus_max......................................: 2       min=2         max=2