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

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
esbuild	0.18.12 -> 0.18.13

---

Release Notes

evanw/esbuild (esbuild)

v0.18.13

Compare Source

• Add the --drop-labels= option (#​2398)

  If you want to conditionally disable some development-only code and have it not be present in the final production bundle, right now the most straightforward way of doing this is to use the --define: flag along with a specially-named global variable. For example, consider the following code:

  function main() {
    DEV && doAnExpensiveCheck()
  }

  You can build this for development and production like this:

  • Development: esbuild --define:DEV=true
  • Production: esbuild --define:DEV=false

  One drawback of this approach is that the resulting code crashes if you don't provide a value for DEV with --define:. In practice this isn't that big of a problem, and there are also various ways to work around this.

  However, another approach that avoids this drawback is to use JavaScript label statements instead. That's what the --drop-labels= flag implements. For example, consider the following code:

  function main() {
    DEV: doAnExpensiveCheck()
  }

  With this release, you can now build this for development and production like this:

  • Development: esbuild
  • Production: esbuild --drop-labels=DEV

  This means that code containing optional development-only checks can now be written such that it's safe to run without any additional configuration. The --drop-labels= flag takes comma-separated list of multiple label names to drop.

• Avoid causing unhandledRejection during shutdown (#​3219)

  All pending esbuild JavaScript API calls are supposed to fail if esbuild's underlying child process is unexpectedly terminated. This can happen if SIGINT is sent to the parent node process with Ctrl+C, for example. Previously doing this could also cause an unhandled promise rejection when esbuild attempted to communicate this failure to its own child process that no longer exists. This release now swallows this communication failure, which should prevent this internal unhandled promise rejection. This change means that you can now use esbuild's JavaScript API with a custom SIGINT handler that extends the lifetime of the node process without esbuild's internals causing an early exit due to an unhandled promise rejection.

• Update browser compatibility table scripts

  The scripts that esbuild uses to compile its internal browser compatibility table have been overhauled. Briefly:

  • Converted from JavaScript to TypeScript
  • Fixed some bugs that resulted in small changes to the table
  • Added caniuse-lite and @mdn/browser-compat-data as new data sources (replacing manually-copied information)

  This change means it's now much easier to keep esbuild's internal compatibility tables up to date. You can review the table changes here if you need to debug something about this change:

  • JS table changes
  • CSS table changes

---

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 has been generated by Mend Renovate. View repository job log here.

[github-actions]

💻 Website Preview

The latest changes are available as preview in: https://a87ca2cc.fets.pages.dev

[github-actions]

✅ 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:node-http,mode:zod}
     ✓ expected_result{server:node-http,mode:zod}
     ✓ 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}
     ✓ no_errors{server:uWebSockets,mode:zod}
     ✓ expected_result{server:uWebSockets,mode:zod}

     checks......................................: 100.00% ✓ 1341852    ✗ 0     
     data_received...............................: 122 MB  676 kB/s
     data_sent...................................: 84 MB   465 kB/s
     http_req_blocked............................: avg=1.39µs   min=600ns   med=1.1µs    max=7.23ms  p(90)=1.8µs   p(95)=2.6µs   
     http_req_connecting.........................: avg=4ns      min=0s      med=0s       max=1.95ms  p(90)=0s      p(95)=0s      
     http_req_duration...........................: avg=185.07µs min=76.5µs  med=150.79µs max=23.01ms p(90)=235.3µs p(95)=288.1µs 
       { expected_response:true }................: avg=185.07µs min=76.5µs  med=150.79µs max=23.01ms p(90)=235.3µs p(95)=288.1µs 
     ✓ { server:node-http,mode:json-schema }.....: avg=199.73µs min=106.7µs med=163.8µs  max=13.94ms p(90)=253.5µs p(95)=303.7µs 
     ✓ { server:node-http,mode:no-schema }.......: avg=190.93µs min=87.2µs  med=151.5µs  max=19.77ms p(90)=237.3µs p(95)=286.77µs
     ✓ { server:node-http,mode:zod }.............: avg=196.93µs min=106.3µs med=164.4µs  max=16.04ms p(90)=250.8µs p(95)=301.8µs 
     ✓ { server:uWebSockets,mode:json-schema }...: avg=176.89µs min=83.4µs  med=142µs    max=23.01ms p(90)=224.2µs p(95)=275.7µs 
     ✓ { server:uWebSockets,mode:no-schema }.....: avg=170.96µs min=76.5µs  med=134.6µs  max=19.44ms p(90)=211.5µs p(95)=263.9µs 
     ✓ { server:uWebSockets,mode:zod }...........: avg=177.95µs min=83.6µs  med=141.7µs  max=18.22ms p(90)=230.8µs p(95)=285.7µs 
     http_req_failed.............................: 0.00%   ✓ 0          ✗ 670926
     http_req_receiving..........................: avg=18.98µs  min=8.2µs   med=14.9µs   max=12.61ms p(90)=27.4µs  p(95)=32.7µs  
     http_req_sending............................: avg=7.89µs   min=3.6µs   med=5.7µs    max=9.06ms  p(90)=11.4µs  p(95)=14.5µs  
     http_req_tls_handshaking....................: avg=0s       min=0s      med=0s       max=0s      p(90)=0s      p(95)=0s      
     http_req_waiting............................: avg=158.19µs min=56.9µs  med=127.8µs  max=22.86ms p(90)=198.9µs p(95)=241.3µs 
     http_reqs...................................: 670926  3727.32757/s
     iteration_duration..........................: avg=262.89µs min=120.6µs med=217.7µs  max=23.29ms p(90)=343.9µs p(95)=427.6µs 
     iterations..................................: 670926  3727.32757/s
     vus.........................................: 1       min=1        max=2   
     vus_max.....................................: 2       min=2        max=2