chore(deps): update dependency esbuild to v0.24.0

renovate[bot] commented 1 month ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	`0.23.1` -> `0.24.0`

Release Notes

evanw/esbuild (esbuild)

### [`v0.24.0`](https://redirect.github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0240) [Compare Source](https://redirect.github.com/evanw/esbuild/compare/v0.23.1...v0.24.0) ***This release deliberately contains backwards-incompatible changes.*** To avoid automatically picking up releases like this, you should either be pinning the exact version of `esbuild` in your `package.json` file (recommended) or be using a version range syntax that only accepts patch upgrades such as `^0.23.0` or `~0.23.0`. See npm's documentation about [semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more information. - Drop support for older platforms ([#3902](https://redirect.github.com/evanw/esbuild/pull/3902)) This release drops support for the following operating system: - macOS 10.15 Catalina This is because the Go programming language dropped support for this operating system version in Go 1.23, and this release updates esbuild from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or later. Note that this only affects the binary esbuild executables that are published to the esbuild npm package. It's still possible to compile esbuild's source code for these older operating systems. If you need to, you can compile esbuild for yourself using an older version of the Go compiler (before Go version 1.23). That might look something like this: git clone https://github.com/evanw/esbuild.git cd esbuild go build ./cmd/esbuild ./esbuild --version - Fix class field decorators in TypeScript if `useDefineForClassFields` is `false` ([#3913](https://redirect.github.com/evanw/esbuild/issues/3913)) Setting the `useDefineForClassFields` flag to `false` in `tsconfig.json` means class fields use the legacy TypeScript behavior instead of the standard JavaScript behavior. Specifically they use assign semantics instead of define semantics (e.g. setters are triggered) and fields without an initializer are not initialized at all. However, when this legacy behavior is combined with standard JavaScript decorators, TypeScript switches to always initializing all fields, even those without initializers. Previously esbuild incorrectly continued to omit field initializers for this edge case. These field initializers in this case should now be emitted starting with this release. - Avoid incorrect cycle warning with `tsconfig.json` multiple inheritance ([#3898](https://redirect.github.com/evanw/esbuild/issues/3898)) TypeScript 5.0 introduced multiple inheritance for `tsconfig.json` files where `extends` can be an array of file paths. Previously esbuild would incorrectly treat files encountered more than once when processing separate subtrees of the multiple inheritance hierarchy as an inheritance cycle. With this release, `tsconfig.json` files containing this edge case should work correctly without generating a warning. - Handle Yarn Plug'n'Play stack overflow with `tsconfig.json` ([#3915](https://redirect.github.com/evanw/esbuild/issues/3915)) Previously a `tsconfig.json` file that `extends` another file in a package with an `exports` map could cause a stack overflow when Yarn's Plug'n'Play resolution was active. This edge case should work now starting with this release. - Work around more issues with Deno 1.31+ ([#3917](https://redirect.github.com/evanw/esbuild/pull/3917)) This version of Deno broke the `stdin` and `stdout` properties on command objects for inherited streams, which matters when you run esbuild's Deno module as the entry point (i.e. when `import.meta.main` is `true`). Previously esbuild would crash in Deno 1.31+ if you ran esbuild like that. This should be fixed starting with this release. This fix was contributed by [@Joshix-1](https://redirect.github.com/Joshix-1).

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] 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[bot] commented 1 month ago

### 💻 Website Preview The latest changes are available as preview in: [https://de60e5c0.fets.pages.dev](https://de60e5c0.fets.pages.dev)

github-actions[bot] commented 1 month ago

✅ Benchmark Results

     ✓ no_errors{server:node-http,mode:no-schema}
     ✓ expected_result{server:node-http,mode:no-schema}
     ✓ no_errors{server:node-http,mode:json-schema}
     ✓ expected_result{server:node-http,mode:json-schema}
     ✓ no_errors{server:uWebSockets,mode:no-schema}
     ✓ expected_result{server:uWebSockets,mode:no-schema}
     ✓ no_errors{server:uWebSockets,mode:json-schema}
     ✓ expected_result{server:uWebSockets,mode:json-schema}

     checks......................................: 100.00% ✓ 921466      ✗ 0     
     data_received...............................: 84 MB   696 kB/s
     data_sent...................................: 59 MB   488 kB/s
     http_req_blocked............................: avg=1.52µs   min=851ns    med=1.47µs   max=266.58µs p(90)=1.92µs   p(95)=2.05µs  
     http_req_connecting.........................: avg=1ns      min=0s       med=0s       max=147.16µs p(90)=0s       p(95)=0s      
     http_req_duration...........................: avg=184.15µs min=115.32µs med=174.79µs max=8.07ms   p(90)=200.58µs p(95)=209.23µs
       { expected_response:true }................: avg=184.15µs min=115.32µs med=174.79µs max=8.07ms   p(90)=200.58µs p(95)=209.23µs
     ✓ { server:node-http,mode:json-schema }.....: avg=196.15µs min=137.68µs med=186.59µs max=6.16ms   p(90)=210.16µs p(95)=218.21µs
     ✓ { server:node-http,mode:no-schema }.......: avg=192.61µs min=130.66µs med=179.97µs max=8.07ms   p(90)=204.17µs p(95)=213.55µs
     ✓ { server:uWebSockets,mode:json-schema }...: avg=178.29µs min=122.4µs  med=170.32µs max=6.42ms   p(90)=191.95µs p(95)=199.02µs
     ✓ { server:uWebSockets,mode:no-schema }.....: avg=171.36µs min=115.32µs med=162.49µs max=7.17ms   p(90)=184.77µs p(95)=192.49µs
     http_req_failed.............................: 0.00%   ✓ 0           ✗ 460733
     http_req_receiving..........................: avg=22.78µs  min=10.75µs  med=22.06µs  max=4.15ms   p(90)=27.14µs  p(95)=29.42µs 
     http_req_sending............................: avg=8.77µs   min=4.97µs   med=8.75µs   max=312.39µs p(90)=11.15µs  p(95)=12.4µs  
     http_req_tls_handshaking....................: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting............................: avg=152.58µs min=91.11µs  med=143.48µs max=8.03ms   p(90)=166.98µs p(95)=175.04µs
     http_reqs...................................: 460733  3839.388547/s
     iteration_duration..........................: avg=255.95µs min=173.98µs med=246.34µs max=8.19ms   p(90)=275.64µs p(95)=286.22µs
     iterations..................................: 460733  3839.388547/s
     vus.........................................: 1       min=1         max=1   
     vus_max.....................................: 2       min=2         max=2

ardatan / feTS