chore(deps): update all non-major dependencies

renovate[bot] commented 2 months ago

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	`22.3.0` -> `22.4.0`
esbuild	`0.23.0` -> `0.23.1`

Release Notes

evanw/esbuild (esbuild)

### [`v0.23.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0231) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.23.0...332727499e62315cff4ecaff9fa8b86336555e46) - Allow using the `node:` import prefix with `es*` targets ([#3821](https://togithub.com/evanw/esbuild/issues/3821)) The [`node:` prefix on imports](https://nodejs.org/api/esm.html#node-imports) is an alternate way to import built-in node modules. For example, `import fs from "fs"` can also be written `import fs from "node:fs"`. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with `--target=node14` so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as `--target=node18,es2022` removes the `node:` prefix because none of the `es*` targets are known to support this feature. This release adds the support for the `node:` flag to esbuild's internal compatibility table for `es*` to allow you to use compound targets like this: ```js // Original code import fs from 'node:fs' fs.open // Old output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "fs"; fs.open; // New output (with --bundle --format=esm --platform=node --target=node18,es2022) import fs from "node:fs"; fs.open; ``` - Fix a panic when using the CLI with invalid build flags if `--analyze` is present ([#3834](https://togithub.com/evanw/esbuild/issues/3834)) Previously esbuild's CLI could crash if it was invoked with flags that aren't valid for a "build" API call and the `--analyze` flag is present. This was caused by esbuild's internals attempting to add a Go plugin (which is how `--analyze` is implemented) to a null build object. The panic has been fixed in this release. - Fix incorrect location of certain error messages ([#3845](https://togithub.com/evanw/esbuild/issues/3845)) This release fixes a regression that caused certain errors relating to variable declarations to be reported at an incorrect location. The regression was introduced in version 0.18.7 of esbuild. - Print comments before case clauses in switch statements ([#3838](https://togithub.com/evanw/esbuild/issues/3838)) With this release, esbuild will attempt to print comments that come before case clauses in switch statements. This is similar to what esbuild already does for comments inside of certain types of expressions. Note that these types of comments are not printed if minification is enabled (specifically whitespace minification). - Fix a memory leak with `pluginData` ([#3825](https://togithub.com/evanw/esbuild/issues/3825)) With this release, the build context's internal `pluginData` cache will now be cleared when starting a new build. This should fix a leak of memory from plugins that return `pluginData` objects from `onResolve` and/or `onLoad` callbacks.

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[bot] commented 2 months ago

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

github-actions[bot] commented 2 months 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% ✓ 885632      ✗ 0     
     data_received...............................: 80 MB   669 kB/s
     data_sent...................................: 56 MB   469 kB/s
     http_req_blocked............................: avg=1.56µs   min=932ns    med=1.52µs   max=323.52µs p(90)=1.98µs   p(95)=2.16µs  
     http_req_connecting.........................: avg=0ns      min=0s       med=0s       max=113.76µs p(90)=0s       p(95)=0s      
     http_req_duration...........................: avg=190.62µs min=128.02µs med=179.38µs max=11.9ms   p(90)=205.29µs p(95)=213.8µs 
       { expected_response:true }................: avg=190.62µs min=128.02µs med=179.38µs max=11.9ms   p(90)=205.29µs p(95)=213.8µs 
     ✓ { server:node-http,mode:json-schema }.....: avg=204.58µs min=150.86µs med=192.83µs max=7.85ms   p(90)=215.81µs p(95)=223.7µs 
     ✓ { server:node-http,mode:no-schema }.......: avg=196.88µs min=139.95µs med=182.29µs max=11.9ms   p(90)=206.03µs p(95)=215.27µs
     ✓ { server:uWebSockets,mode:json-schema }...: avg=185.45µs min=135.07µs med=175.7µs  max=7.27ms   p(90)=197.51µs p(95)=203.77µs
     ✓ { server:uWebSockets,mode:no-schema }.....: avg=177.31µs min=128.02µs med=167.08µs max=7.39ms   p(90)=189.1µs  p(95)=196.18µs
     http_req_failed.............................: 0.00%   ✓ 0           ✗ 442816
     http_req_receiving..........................: avg=23.49µs  min=12.09µs  med=23.1µs   max=1.7ms    p(90)=28.6µs   p(95)=30.49µs 
     http_req_sending............................: avg=9µs      min=5.25µs   med=9.12µs   max=463.32µs p(90)=11.93µs  p(95)=13.29µs 
     http_req_tls_handshaking....................: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting............................: avg=158.13µs min=101.54µs med=147.08µs max=11.84ms  p(90)=170.54µs p(95)=178.72µs
     http_reqs...................................: 442816  3690.092155/s
     iteration_duration..........................: avg=266.09µs min=188.08µs med=254.27µs max=12.05ms  p(90)=282.57µs p(95)=293.48µs
     iterations..................................: 442816  3690.092155/s
     vus.........................................: 1       min=1         max=1   
     vus_max.....................................: 2       min=2         max=2

ardatan / feTS