chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/core (source)	7.26.7 -> 7.26.8
@babel/preset-env (source)	7.26.7 -> 7.26.8
esbuild	0.24.2 -> 0.25.0

---

Release Notes

babel/babel (@​babel/core)

v7.26.8

v7.26.8 (2025-02-08)

🏠 Internal

• babel-preset-env
  • #​17097 Update dependency babel-plugin-polyfill-corejs3 to ^0.11.0

evanw/esbuild (esbuild)

v0.25.0

Compare Source

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.24.0 or ~0.24.0. See npm's documentation about semver for more information.

• Restrict access to esbuild's development server (GHSA-67mh-4wv8-2f99)

  This change addresses esbuild's first security vulnerability report. Previously esbuild set the Access-Control-Allow-Origin header to * to allow esbuild's development server to be flexible in how it's used for development. However, this allows the websites you visit to make HTTP requests to esbuild's local development server, which gives read-only access to your source code if the website were to fetch your source code's specific URL. You can read more information in the report.

  Starting with this release, CORS will now be disabled, and requests will now be denied if the host does not match the one provided to --serve=. The default host is 0.0.0.0, which refers to all of the IP addresses that represent the local machine (e.g. both 127.0.0.1 and 192.168.0.1). If you want to customize anything about esbuild's development server, you can put a proxy in front of esbuild and modify the incoming and/or outgoing requests.

  In addition, the serve() API call has been changed to return an array of hosts instead of a single host string. This makes it possible to determine all of the hosts that esbuild's development server will accept.

  Thanks to @​sapphi-red for reporting this issue.

• Delete output files when a build fails in watch mode (#​3643)

  It has been requested for esbuild to delete files when a build fails in watch mode. Previously esbuild left the old files in place, which could cause people to not immediately realize that the most recent build failed. With this release, esbuild will now delete all output files if a rebuild fails. Fixing the build error and triggering another rebuild will restore all output files again.

• Fix correctness issues with the CSS nesting transform (#​3620, #​3877, #​3933, #​3997, #​4005, #​4037, #​4038)

  This release fixes the following problems:

  • Naive expansion of CSS nesting can result in an exponential blow-up of generated CSS if each nesting level has multiple selectors. Previously esbuild sometimes collapsed individual nesting levels using :is() to limit expansion. However, this collapsing wasn't correct in some cases, so it has been removed to fix correctness issues.

    /* Original code */
    .parent {
      > .a,
      > .b1 > .b2 {
        color: red;
      }
    }
    
    /* Old output (with --supported:nesting=false) */
    .parent > :is(.a, .b1 > .b2) {
      color: red;
    }
    
    /* New output (with --supported:nesting=false) */
    .parent > .a,
    .parent > .b1 > .b2 {
      color: red;
    }

    Thanks to @​tim-we for working on a fix.

  • The & CSS nesting selector can be repeated multiple times to increase CSS specificity. Previously esbuild ignored this possibility and incorrectly considered && to have the same specificity as &. With this release, this should now work correctly:

    /* Original code (color should be red) */
    div {
      && { color: red }
      & { color: blue }
    }
    
    /* Old output (with --supported:nesting=false) */
    div {
      color: red;
    }
    div {
      color: blue;
    }
    
    /* New output (with --supported:nesting=false) */
    div:is(div) {
      color: red;
    }
    div {
      color: blue;
    }

    Thanks to @​CPunisher for working on a fix.

  • Previously transforming nested CSS incorrectly removed leading combinators from within pseudoclass selectors such as :where(). This edge case has been fixed and how has test coverage.

    /* Original code */
    a b:has(> span) {
      a & {
        color: green;
      }
    }
    
    /* Old output (with --supported:nesting=false) */
    a :is(a b:has(span)) {
      color: green;
    }
    
    /* New output (with --supported:nesting=false) */
    a :is(a b:has(> span)) {
      color: green;
    }

    This fix was contributed by @​NoremacNergfol.

  • The CSS minifier contains logic to remove the & selector when it can be implied, which happens when there is only one and it's the leading token. However, this logic was incorrectly also applied to selector lists inside of pseudo-class selectors such as :where(). With this release, the minifier will now avoid applying this logic in this edge case:

    /* Original code */
    .a {
      & .b { color: red }
      :where(& .b) { color: blue }
    }
    
    /* Old output (with --minify) */
    .a{.b{color:red}:where(.b){color:#​00f}}
    
    /* New output (with --minify) */
    .a{.b{color:red}:where(& .b){color:#​00f}}

• Fix some correctness issues with source maps (#​1745, #​3183, #​3613, #​3982)

  Previously esbuild incorrectly treated source map path references as file paths instead of as URLs. With this release, esbuild will now treat source map path references as URLs. This fixes the following problems with source maps:

  • File names in sourceMappingURL that contained a space previously did not encode the space as %20, which resulted in JavaScript tools (including esbuild) failing to read that path back in when consuming the generated output file. This should now be fixed.

  • Absolute URLs in sourceMappingURL that use the file:// scheme previously attempted to read from a folder called file:. These URLs should now be recognized and parsed correctly.

  • Entries in the sources array in the source map are now treated as URLs instead of file paths. The correct behavior for this is much more clear now that source maps has a formal specification. Many thanks to those who worked on the specification.

• Fix incorrect package for @esbuild/netbsd-arm64 (#​4018)

  Due to a copy+paste typo, the binary published to @esbuild/netbsd-arm64 was not actually for arm64, and didn't run in that environment. This release should fix running esbuild in that environment (NetBSD on 64-bit ARM). Sorry about the mistake.

• Fix a minification bug with bitwise operators and bigints (#​4065)

  This change removes an incorrect assumption in esbuild that all bitwise operators result in a numeric integer. That assumption was correct up until the introduction of bigints in ES2020, but is no longer correct because almost all bitwise operators now operate on both numbers and bigints. Here's an example of the incorrect minification:

  // Original code
  if ((a & b) !== 0) found = true
  
  // Old output (with --minify)
  a&b&&(found=!0);
  
  // New output (with --minify)
  (a&b)!==0&&(found=!0);

• Fix esbuild incorrectly rejecting valid TypeScript edge case (#​4027)

  The following TypeScript code is valid:

  export function open(async?: boolean): void {
    console.log(async as boolean)
  }

  Before this version, esbuild would fail to parse this with a syntax error as it expected the token sequence async as ... to be the start of an async arrow function expression async as => .... This edge case should be parsed correctly by esbuild starting with this release.

• Transform BigInt values into constructor calls when unsupported (#​4049)

  Previously esbuild would refuse to compile the BigInt literals (such as 123n) if they are unsupported in the configured target environment (such as with --target=es6). The rationale was that they cannot be polyfilled effectively because they change the behavior of JavaScript's arithmetic operators and JavaScript doesn't have operator overloading.

  However, this prevents using esbuild with certain libraries that would otherwise work if BigInt literals were ignored, such as with old versions of the buffer library before the library fixed support for running in environments without BigInt support. So with this release, esbuild will now turn BigInt literals into BigInt constructor calls (so 123n becomes BigInt(123)) and generate a warning in this case. You can turn off the warning with --log-override:bigint=silent or restore the warning to an error with --log-override:bigint=error if needed.

• Change how console API dropping works (#​4020)

  Previously the --drop:console feature replaced all method calls off of the console global with undefined regardless of how long the property access chain was (so it applied to console.log() and console.log.call(console) and console.log.not.a.method()). However, it was pointed out that this breaks uses of console.log.bind(console). That's also incompatible with Terser's implementation of the feature, which is where this feature originally came from (it does support bind). So with this release, using this feature with esbuild will now only replace one level of method call (unless extended by call or apply) and will replace the method being called with an empty function in complex cases:

  // Original code
  const x = console.log('x')
  const y = console.log.call(console, 'y')
  const z = console.log.bind(console)('z')
  
  // Old output (with --drop-console)
  const x = void 0;
  const y = void 0;
  const z = (void 0)("z");
  
  // New output (with --drop-console)
  const x = void 0;
  const y = void 0;
  const z = (() => {
  }).bind(console)("z");

  This should more closely match Terser's existing behavior.

• Allow BigInt literals as define values

  With this release, you can now use BigInt literals as define values, such as with --define:FOO=123n. Previously trying to do this resulted in a syntax error.

• Fix a bug with resolve extensions in node_modules (#​4053)

  The --resolve-extensions= option lets you specify the order in which to try resolving implicit file extensions. For complicated reasons, esbuild reorders TypeScript file extensions after JavaScript ones inside of node_modules so that JavaScript source code is always preferred to TypeScript source code inside of dependencies. However, this reordering had a bug that could accidentally change the relative order of TypeScript file extensions if one of them was a prefix of the other. That bug has been fixed in this release. You can see the issue for details.

• Better minification of statically-determined switch cases (#​4028)

  With this release, esbuild will now try to trim unused code within switch statements when the test expression and case expressions are primitive literals. This can arise when the test expression is an identifier that is substituted for a primitive literal at compile time. For example:

  // Original code
  switch (MODE) {
    case 'dev':
      installDevToolsConsole()
      break
    case 'prod':
      return
    default:
      throw new Error
  }
  
  // Old output (with --minify '--define:MODE="prod"')
  switch("prod"){case"dev":installDevToolsConsole();break;case"prod":return;default:throw new Error}
  
  // New output (with --minify '--define:MODE="prod"')
  return;

• Emit /* @​__KEY__ */ for string literals derived from property names (#​4034)

  Property name mangling is an advanced feature that shortens certain property names for better minification (I say "advanced feature" because it's very easy to break your code with it). Sometimes you need to store a property name in a string, such as obj.get('foo') instead of obj.foo. JavaScript minifiers such as esbuild and Terser have a convention where a /* @​__KEY__ */ comment before the string makes it behave like a property name. So obj.get(/* @​__KEY__ */ 'foo') allows the contents of the string 'foo' to be shortened.

  However, esbuild sometimes itself generates string literals containing property names when transforming code, such as when lowering class fields to ES6 or when transforming TypeScript decorators. Previously esbuild didn't generate its own /* @​__KEY__ */ comments in this case, which means that minifying your code by running esbuild again on its own output wouldn't work correctly (this does not affect people that both minify and transform their code in a single step).

  With this release, esbuild will now generate /* @​__KEY__ */ comments for property names in generated string literals. To avoid lots of unnecessary output for people that don't use this advanced feature, the generated comments will only be present when the feature is active. If you want to generate the comments but not actually mangle any property names, you can use a flag that has no effect such as --reserve-props=., which tells esbuild to not mangle any property names (but still activates this feature).

• The text loader now strips the UTF-8 BOM if present (#​3935)

  Some software (such as Notepad on Windows) can create text files that start with the three bytes 0xEF 0xBB 0xBF, which is referred to as the "byte order mark". This prefix is intended to be removed before using the text. Previously esbuild's text loader included this byte sequence in the string, which turns into a prefix of \uFEFF in a JavaScript string when decoded from UTF-8. With this release, esbuild's text loader will now remove these bytes when they occur at the start of the file.

• Omit legal comment output files when empty (#​3670)

  Previously configuring esbuild with --legal-comment=external or --legal-comment=linked would always generate a .LEGAL.txt output file even if it was empty. Starting with this release, esbuild will now only do this if the file will be non-empty. This should result in a more organized output directory in some cases.

• Update Go from 1.23.1 to 1.23.5 (#​4056, #​4057)

  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.

  This PR was contributed by @​MikeWillCook.

• Allow passing a port of 0 to the development server (#​3692)

  Unix sockets interpret a port of 0 to mean "pick a random unused port in the ephemeral port range". However, esbuild's default behavior when the port is not specified is to pick the first unused port starting from 8000 and upward. This is more convenient because port 8000 is typically free, so you can for example restart the development server and reload your app in the browser without needing to change the port in the URL. Since esbuild is written in Go (which does not have optional fields like JavaScript), not specifying the port in Go means it defaults to 0, so previously passing a port of 0 to esbuild caused port 8000 to be picked.

  Starting with this release, passing a port of 0 to esbuild when using the CLI or the JS API will now pass port 0 to the OS, which will pick a random ephemeral port. To make this possible, the Port option in the Go API has been changed from uint16 to int (to allow for additional sentinel values) and passing a port of -1 in Go now picks a random port. Both the CLI and JS APIs now remap an explicitly-provided port of 0 into -1 for the internal Go API.

  Another option would have been to change Port in Go from uint16 to *uint16 (Go's closest equivalent of number | undefined). However, that would make the common case of providing an explicit port in Go very awkward as Go doesn't support taking the address of integer constants. This tradeoff isn't worth it as picking a random ephemeral port is a rare use case. So the CLI and JS APIs should now match standard Unix behavior when the port is 0, but you need to use -1 instead with Go API.

• Minification now avoids inlining constants with direct eval (#​4055)

  Direct eval can be used to introduce a new variable like this:

  const variable = false
  ;(function () {
    eval("var variable = true")
    console.log(variable)
  })()

  Previously esbuild inlined variable here (which became false), which changed the behavior of the code. This inlining is now avoided, but please keep in mind that direct eval breaks many assumptions that JavaScript tools hold about normal code (especially when bundling) and I do not recommend using it. There are usually better alternatives that have a more localized impact on your code. You can read more about this here: https://esbuild.github.io/link/direct-eval/

---

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.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

✅ @benchmarks/node-fetch results (consumeBody)

   ✓ active_handles.................: avg=140.50561 min=38      med=141     max=197     p(90)=160     p(95)=163    
     data_received..................: 20 MB  649 kB/s
     data_sent......................: 13 MB  416 kB/s
     http_req_blocked...............: avg=4.13µs    min=652ns   med=1.26µs  max=7.51ms  p(90)=2.01µs  p(95)=2.26µs 
     http_req_connecting............: avg=1.99µs    min=0s      med=0s      max=5.59ms  p(90)=0s      p(95)=0s     
     http_req_duration..............: avg=23.49ms   min=7.03ms  med=22.83ms max=1.17s   p(90)=29.44ms p(95)=30.98ms
       { expected_response:true }...: avg=23.49ms   min=7.03ms  med=22.83ms max=1.17s   p(90)=29.44ms p(95)=30.98ms
     http_req_failed................: 0.00%  ✓ 0           ✗ 127314
     http_req_receiving.............: avg=33.62µs   min=9.59µs  med=24.65µs max=16.96ms p(90)=38.93µs p(95)=45.17µs
     http_req_sending...............: avg=11µs      min=3.37µs  med=6.08µs  max=8.79ms  p(90)=9.96µs  p(95)=13.72µs
     http_req_tls_handshaking.......: avg=0s        min=0s      med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_waiting...............: avg=23.44ms   min=6.99ms  med=22.79ms max=1.17s   p(90)=29.4ms  p(95)=30.93ms
     http_reqs......................: 127314 4243.045913/s
     iteration_duration.............: avg=47.09ms   min=24.29ms med=45.31ms max=1.21s   p(90)=51.37ms p(95)=57.67ms
     iterations.....................: 63634  2120.756426/s
     vus............................: 100    min=100       max=100 
     vus_max........................: 100    min=100       max=100 

[github-actions]

✅ @benchmarks/server results (native)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 206306      ✗ 0     
     data_received..................: 21 MB   691 kB/s
     data_sent......................: 8.3 MB  275 kB/s
     http_req_blocked...............: avg=1.5µs    min=962ns    med=1.26µs   max=306.59µs p(90)=2.01µs   p(95)=2.19µs  
     http_req_connecting............: avg=1ns      min=0s       med=0s       max=117.28µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=227.51µs min=174.33µs med=216.58µs max=10.43ms  p(90)=243.34µs p(95)=253.99µs
       { expected_response:true }...: avg=227.51µs min=174.33µs med=216.58µs max=10.43ms  p(90)=243.34µs p(95)=253.99µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 103153
     http_req_receiving.............: avg=25.7µs   min=13.72µs  med=23.99µs  max=2.52ms   p(90)=31.06µs  p(95)=33.7µs  
     http_req_sending...............: avg=6.51µs   min=4.21µs   med=5.74µs   max=1.7ms    p(90)=8.31µs   p(95)=9.11µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=195.29µs min=147.33µs med=184.4µs  max=8.68ms   p(90)=208.29µs p(95)=217.96µs
     http_reqs......................: 103153  3438.319046/s
     iteration_duration.............: avg=286.27µs min=219.58µs med=274.77µs max=10.54ms  p(90)=304.73µs p(95)=317.35µs
     iterations.....................: 103153  3438.319046/s
     vus............................: 1       min=1         max=1   
     vus_max........................: 1       min=1         max=1   

[github-actions]

✅ @benchmarks/node-fetch results (noConsumeBody)

   ✓ active_handles.................: avg=140.659804 min=26      med=141     max=179     p(90)=159     p(95)=164    
     data_received..................: 21 MB  691 kB/s
     data_sent......................: 13 MB  447 kB/s
     http_req_blocked...............: avg=3.44µs     min=601ns   med=1.34µs  max=5.82ms  p(90)=2.02µs  p(95)=2.29µs 
     http_req_connecting............: avg=1.69µs     min=0s      med=0s      max=5.77ms  p(90)=0s      p(95)=0s     
     http_req_duration..............: avg=22.07ms    min=3.33ms  med=21.5ms  max=1.15s   p(90)=27.8ms  p(95)=29.42ms
       { expected_response:true }...: avg=22.07ms    min=3.33ms  med=21.5ms  max=1.15s   p(90)=27.8ms  p(95)=29.42ms
     http_req_failed................: 0.00%  ✓ 0           ✗ 135457
     http_req_receiving.............: avg=32.67µs    min=9.45µs  med=23.5µs  max=15.89ms p(90)=37.92µs p(95)=44.58µs
     http_req_sending...............: avg=10.89µs    min=3.21µs  med=6.45µs  max=21.97ms p(90)=9.88µs  p(95)=13.7µs 
     http_req_tls_handshaking.......: avg=0s         min=0s      med=0s      max=0s      p(90)=0s      p(95)=0s     
     http_req_waiting...............: avg=22.03ms    min=3.29ms  med=21.46ms max=1.15s   p(90)=27.75ms p(95)=29.36ms
     http_reqs......................: 135457 4514.698747/s
     iteration_duration.............: avg=44.26ms    min=14.01ms med=42.63ms max=1.18s   p(90)=48.78ms p(95)=54.26ms
     iterations.....................: 67711  2256.766109/s
     vus............................: 100    min=100       max=100 
     vus_max........................: 100    min=100       max=100 

[github-actions]

✅ @benchmarks/server results (ponyfill)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 301450      ✗ 0     
     data_received..................: 30 MB   990 kB/s
     data_sent......................: 12 MB   402 kB/s
     http_req_blocked...............: avg=1.39µs   min=882ns    med=1.19µs   max=231.75µs p(90)=1.85µs   p(95)=2.02µs  
     http_req_connecting............: avg=0ns      min=0s       med=0s       max=127.15µs p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=137.25µs min=95.24µs  med=132.55µs max=5.93ms   p(90)=155.55µs p(95)=163.14µs
       { expected_response:true }...: avg=137.25µs min=95.24µs  med=132.55µs max=5.93ms   p(90)=155.55µs p(95)=163.14µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 150725
     http_req_receiving.............: avg=24.14µs  min=11.93µs  med=22.51µs  max=2.82ms   p(90)=29.99µs  p(95)=32.77µs 
     http_req_sending...............: avg=6.16µs   min=4.02µs   med=5.28µs   max=465.38µs p(90)=7.98µs   p(95)=8.57µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=106.94µs min=68.66µs  med=102µs    max=5.79ms   p(90)=121.77µs p(95)=127.93µs
     http_reqs......................: 150725  5023.951632/s
     iteration_duration.............: avg=194.53µs min=140.79µs med=188.99µs max=6.13ms   p(90)=215.62µs p(95)=225.72µs
     iterations.....................: 150725  5023.951632/s
     vus............................: 1       min=1         max=1   
     vus_max........................: 1       min=1         max=1   

[github-actions]

✅ @benchmarks/server results (undici)

     ✓ no-errors
     ✓ expected-result

   ✓ checks.........................: 100.00% ✓ 195572      ✗ 0    
     data_received..................: 20 MB   655 kB/s
     data_sent......................: 7.8 MB  261 kB/s
     http_req_blocked...............: avg=1.4µs    min=871ns    med=1.2µs    max=285.79µs p(90)=1.89µs   p(95)=2.05µs  
     http_req_connecting............: avg=1ns      min=0s       med=0s       max=161µs    p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=243.1µs  min=179.55µs med=228.64µs max=37.54ms  p(90)=268.63µs p(95)=286.86µs
       { expected_response:true }...: avg=243.1µs  min=179.55µs med=228.64µs max=37.54ms  p(90)=268.63µs p(95)=286.86µs
     http_req_failed................: 0.00%   ✓ 0           ✗ 97786
     http_req_receiving.............: avg=26.56µs  min=13.46µs  med=23.68µs  max=2.39ms   p(90)=31.72µs  p(95)=38.3µs  
     http_req_sending...............: avg=6.51µs   min=4.04µs   med=5.86µs   max=592.21µs p(90)=8.25µs   p(95)=8.95µs  
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s       p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=210.02µs min=152.36µs med=196.45µs max=37.47ms  p(90)=230.91µs p(95)=246.69µs
     http_reqs......................: 97786   3259.424734/s
     iteration_duration.............: avg=302.22µs min=222.62µs med=287.07µs max=37.66ms  p(90)=329.83µs p(95)=350.99µs
     iterations.....................: 97786   3259.424734/s
     vus............................: 1       min=1         max=1  
     vus_max........................: 1       min=1         max=1