chore(deps): update driver adapters directory (patch)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/node (source)	20.10.4 -> 20.10.8
esbuild	0.19.8 -> 0.19.12
tsup (source)	8.0.1 -> 8.0.2

---

Release Notes

evanw/esbuild (esbuild)

v0.19.12

Compare Source

• The "preserve" JSX mode now preserves JSX text verbatim (#​3605)

  The JSX specification deliberately doesn't specify how JSX text is supposed to be interpreted and there is no canonical way to interpret JSX text. Two most popular interpretations are Babel and TypeScript. Yes they are different (esbuild deliberately follows TypeScript by the way).

  Previously esbuild normalized text to the TypeScript interpretation when the "preserve" JSX mode is active. However, "preserve" should arguably reproduce the original JSX text verbatim so that whatever JSX transform runs after esbuild is free to interpret it however it wants. So with this release, esbuild will now pass JSX text through unmodified:

  // Original code
  let el =
    <a href={'/'} title='&apos;&quot;'> some text
      {foo}
        more text </a>
  
  // Old output (with --loader=jsx --jsx=preserve)
  let el = <a href="/" title={`'"`}>
    {" some text"}
    {foo}
    {"more text "}
  </a>;
  
  // New output (with --loader=jsx --jsx=preserve)
  let el = <a href={"/"} title='&apos;&quot;'> some text
      {foo}
        more text </a>;

• Allow JSX elements as JSX attribute values

  JSX has an obscure feature where you can use JSX elements in attribute position without surrounding them with {...}. It looks like this:

  let el = <div data-ab=<><a/><b/></>/>;

  I think I originally didn't implement it even though it's part of the JSX specification because it previously didn't work in TypeScript (and potentially also in Babel?). However, support for it was silently added in TypeScript 4.8 without me noticing and Babel has also since fixed their bugs regarding this feature. So I'm adding it to esbuild too now that I know it's widely supported.

  Keep in mind that there is some ongoing discussion about removing this feature from JSX. I agree that the syntax seems out of place (it does away with the elegance of "JSX is basically just XML with {...} escapes" for something arguably harder to read, which doesn't seem like a good trade-off), but it's in the specification and TypeScript and Babel both implement it so I'm going to have esbuild implement it too. However, I reserve the right to remove it from esbuild if it's ever removed from the specification in the future. So use it with caution.

• Fix a bug with TypeScript type parsing (#​3574)

  This release fixes a bug with esbuild's TypeScript parser where a conditional type containing a union type that ends with an infer type that ends with a constraint could fail to parse. This was caused by the "don't parse a conditional type" flag not getting passed through the union type parser. Here's an example of valid TypeScript code that previously failed to parse correctly:

  type InferUnion<T> = T extends { a: infer U extends number } | infer U extends number ? U : never

v0.19.11

Compare Source

• Fix TypeScript-specific class transform edge case (#​3559)

  The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

  // Original code
  class Foo extends Bar {
    #private = 1;
    public: any;
    constructor() {
      super();
    }
  }
  
  // Old output (with esbuild v0.19.9)
  class Foo extends Bar {
    constructor() {
      super();
      this.#private = 1;
    }
    #private;
  }
  
  // Old output (with esbuild v0.19.10)
  class Foo extends Bar {
    constructor() {
      this.#private = 1;
      super();
    }
    #private;
  }
  
  // New output
  class Foo extends Bar {
    #private = 1;
    constructor() {
      super();
    }
  }

• Minifier: allow reording a primitive past a side-effect (#​3568)

  The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

  // Original code
  function f() {
    let x = false;
    let y = x;
    const boolean = y;
    let frag = $.template(`<p contenteditable="${boolean}">hello world</p>`);
    return frag;
  }
  
  // Old output (with --minify)
  function f(){const e=!1;return $.template(`<p contenteditable="${e}">hello world</p>`)}
  
  // New output (with --minify)
  function f(){return $.template('<p contenteditable="false">hello world</p>')}

• Minifier: consider properties named using known Symbol instances to be side-effect free (#​3561)

  Many things in JavaScript can have side effects including property accesses and ToString operations, so using a symbol such as Symbol.iterator as a computed property name is not obviously side-effect free. This release adds a special case for known Symbol instances so that they are considered side-effect free when used as property names. For example, this class declaration will now be considered side-effect free:

  class Foo {
    *[Symbol.iterator]() {
    }
  }

• Provide the stop() API in node to exit esbuild's child process (#​3558)

  You can now call stop() in esbuild's node API to exit esbuild's child process to reclaim the resources used. It only makes sense to do this for a long-lived node process when you know you will no longer be making any more esbuild API calls. It is not necessary to call this to allow node to exit, and it's advantageous to not call this in between calls to esbuild's API as sharing a single long-lived esbuild child process is more efficient than re-creating a new esbuild child process for every API call. This API call used to exist but was removed in version 0.9.0. This release adds it back due to a user request.

v0.19.10

Compare Source

• Fix glob imports in TypeScript files (#​3319)

  This release fixes a problem where bundling a TypeScript file containing a glob import could emit a call to a helper function that doesn't exist. The problem happened because esbuild's TypeScript transformation removes unused imports (which is required for correctness, as they may be type-only imports) and esbuild's glob import transformation wasn't correctly marking the imported helper function as used. This wasn't caught earlier because most of esbuild's glob import tests were written in JavaScript, not in TypeScript.

• Fix require() glob imports with bundling disabled (#​3546)

  Previously require() calls containing glob imports were incorrectly transformed when bundling was disabled. All glob imports should only be transformed when bundling is enabled. This bug has been fixed.

• Fix a panic when transforming optional chaining with define (#​3551, #​3554)

  This release fixes a case where esbuild could crash with a panic, which was triggered by using define to replace an expression containing an optional chain. Here is an example:

  // Original code
  console.log(process?.env.SHELL)
  
  // Old output (with --define:process.env={})
  /* panic: Internal error (while parsing "<stdin>") */
  
  // New output (with --define:process.env={})
  var define_process_env_default = {};
  console.log(define_process_env_default.SHELL);

  This fix was contributed by @​hi-ogawa.

• Work around a bug in node's CommonJS export name detector (#​3544)

  The export names of a CommonJS module are dynamically-determined at run time because CommonJS exports are properties on a mutable object. But the export names of an ES module are statically-determined at module instantiation time by using import and export syntax and cannot be changed at run time.

  When you import a CommonJS module into an ES module in node, node scans over the source code to attempt to detect the set of export names that the CommonJS module will end up using. That statically-determined set of names is used as the set of names that the ES module is allowed to import at module instantiation time. However, this scan appears to have bugs (or at least, can cause false positives) because it doesn't appear to do any scope analysis. Node will incorrectly consider the module to export something even if the assignment is done to a local variable instead of to the module-level exports object. For example:

  // confuseNode.js
  exports.confuseNode = function(exports) {
    // If this local is called "exports", node incorrectly
    // thinks this file has an export called "notAnExport".
    exports.notAnExport = function() {
    };
  };

  You can see that node incorrectly thinks the file confuseNode.js has an export called notAnExport when that file is loaded in an ES module context:

  $ node -e 'import("./confuseNode.js").then(console.log)'
  [Module: null prototype] {
    confuseNode: [Function (anonymous)],
    default: { confuseNode: [Function (anonymous)] },
    notAnExport: undefined
  }

  To avoid this, esbuild will now rename local variables that use the names exports and module when generating CommonJS output for the node platform.

• Fix the return value of esbuild's super() shim (#​3538)

  Some people write constructor methods that use the return value of super() instead of using this. This isn't too common because TypeScript doesn't let you do that but it can come up when writing JavaScript. Previously esbuild's class lowering transform incorrectly transformed the return value of super() into undefined. With this release, the return value of super() will now be this instead:

  // Original code
  class Foo extends Object {
    field
    constructor() {
      console.log(typeof super())
    }
  }
  new Foo
  
  // Old output (with --target=es6)
  class Foo extends Object {
    constructor() {
      var __super = (...args) => {
        super(...args);
        __publicField(this, "field");
      };
      console.log(typeof __super());
    }
  }
  new Foo();
  
  // New output (with --target=es6)
  class Foo extends Object {
    constructor() {
      var __super = (...args) => {
        super(...args);
        __publicField(this, "field");
        return this;
      };
      console.log(typeof __super());
    }
  }
  new Foo();

• Terminate the Go GC when esbuild's stop() API is called (#​3552)

  If you use esbuild with WebAssembly and pass the worker: false flag to esbuild.initialize(), then esbuild will run the WebAssembly module on the main thread. If you do this within a Deno test and that test calls esbuild.stop() to clean up esbuild's resources, Deno may complain that a setTimeout() call lasted past the end of the test. This happens when the Go is in the middle of a garbage collection pass and has scheduled additional ongoing garbage collection work. Normally calling esbuild.stop() will terminate the web worker that the WebAssembly module runs in, which will terminate the Go GC, but that doesn't happen if you disable the web worker with worker: false.

  With this release, esbuild will now attempt to terminate the Go GC in this edge case by calling clearTimeout() on these pending timeouts.

• Apply /* @​__NO_SIDE_EFFECTS__ */ on tagged template literals (#​3511)

  Tagged template literals that reference functions annotated with a @__NO_SIDE_EFFECTS__ comment are now able to be removed via tree-shaking if the result is unused. This is a convention from Rollup. Here is an example:

  // Original code
  const html = /* @​__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b })
  html`<a>remove</a>`
  x = html`<b>keep</b>`
  
  // Old output (with --tree-shaking=true)
  const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
  html`<a>remove</a>`;
  x = html`<b>keep</b>`;
  
  // New output (with --tree-shaking=true)
  const html = /* @&#8203;__NO_SIDE_EFFECTS__ */ (a, ...b) => ({ a, b });
  x = html`<b>keep</b>`;

  Note that this feature currently only works within a single file, so it's not especially useful. This feature does not yet work across separate files. I still recommend using @__PURE__ annotations instead of this feature, as they have wider tooling support. The drawback of course is that @__PURE__ annotations need to be added at each call site, not at the declaration, and for non-call expressions such as template literals you need to wrap the expression in an IIFE (immediately-invoked function expression) to create a call expression to apply the @__PURE__ annotation to.

• Publish builds for IBM AIX PowerPC 64-bit (#​3549)

  This release publishes a binary executable to npm for IBM AIX PowerPC 64-bit, which means that in theory esbuild can now be installed in that environment with npm install esbuild. This hasn't actually been tested yet. If you have access to such a system, it would be helpful to confirm whether or not doing this actually works.

v0.19.9

Compare Source

• Add support for transforming new CSS gradient syntax for older browsers

  The specification called CSS Images Module Level 4 introduces new CSS gradient syntax for customizing how the browser interpolates colors in between color stops. You can now control the color space that the interpolation happens in as well as (for "polar" color spaces) control whether hue angle interpolation happens clockwise or counterclockwise. You can read more about this in Mozilla's blog post about new CSS gradient features.

  With this release, esbuild will now automatically transform this syntax for older browsers in the target list. For example, here's a gradient that should appear as a rainbow in a browser that supports this new syntax:

  /* Original code */
  .rainbow-gradient {
    width: 100px;
    height: 100px;
    background: linear-gradient(in hsl longer hue, #​7ff, #​77f);
  }
  
  /* New output (with --target=chrome99) */
  .rainbow-gradient {
    width: 100px;
    height: 100px;
    background:
      linear-gradient(
        #​77ffff,
        #​77ffaa 12.5%,
        #​77ff80 18.75%,
        #​84ff77 21.88%,
        #​99ff77 25%,
        #eeff77 37.5%,
        #fffb77 40.62%,
        #ffe577 43.75%,
        #ffbb77 50%,
        #ff9077 56.25%,
        #ff7b77 59.38%,
        #ff7788 62.5%,
        #ff77dd 75%,
        #ff77f2 78.12%,
        #f777ff 81.25%,
        #cc77ff 87.5%,
        #​7777ff);
  }

  You can now use this syntax in your CSS source code and esbuild will automatically convert it to an equivalent gradient for older browsers. In addition, esbuild will now also transform "double position" and "transition hint" syntax for older browsers as appropriate:

  /* Original code */
  .stripes {
    width: 100px;
    height: 100px;
    background: linear-gradient(#e65 33%, #ff2 33% 67%, #​99e 67%);
  }
  .glow {
    width: 100px;
    height: 100px;
    background: radial-gradient(white 10%, 20%, black);
  }
  
  /* New output (with --target=chrome33) */
  .stripes {
    width: 100px;
    height: 100px;
    background:
      linear-gradient(
        #e65 33%,
        #ff2 33%,
        #ff2 67%,
        #​99e 67%);
  }
  .glow {
    width: 100px;
    height: 100px;
    background:
      radial-gradient(
        #ffffff 10%,
        #aaaaaa 12.81%,
        #​959595 15.62%,
        #​7b7b7b 21.25%,
        #​5a5a5a 32.5%,
        #​444444 43.75%,
        #​323232 55%,
        #​161616 77.5%,
        #​000000);
  }

  You can see visual examples of these new syntax features by looking at esbuild's gradient transformation tests.

  If necessary, esbuild will construct a new gradient that approximates the original gradient by recursively splitting the interval in between color stops until the approximation error is within a small threshold. That is why the above output CSS contains many more color stops than the input CSS.

  Note that esbuild deliberately replaces the original gradient with the approximation instead of inserting the approximation before the original gradient as a fallback. The latest version of Firefox has multiple gradient rendering bugs (including incorrect interpolation of partially-transparent colors and interpolating non-sRGB colors using the incorrect color space). If esbuild didn't replace the original gradient, then Firefox would use the original gradient instead of the fallback the appearance would be incorrect in Firefox. In other words, the latest version of Firefox supports modern gradient syntax but interprets it incorrectly.

• Add support for color(), lab(), lch(), oklab(), oklch(), and hwb() in CSS

  CSS has recently added lots of new ways of specifying colors. You can read more about this in Chrome's blog post about CSS color spaces.

  This release adds support for minifying colors that use the color(), lab(), lch(), oklab(), oklch(), or hwb() syntax and/or transforming these colors for browsers that don't support it yet:

  /* Original code */
  div {
    color: hwb(90deg 20% 40%);
    background: color(display-p3 1 0 0);
  }
  
  /* New output (with --target=chrome99) */
  div {
    color: #​669933;
    background: #ff0f0e;
    background: color(display-p3 1 0 0);
  }

  As you can see, colors outside of the sRGB color space such as color(display-p3 1 0 0) are mapped back into the sRGB gamut and inserted as a fallback for browsers that don't support the new color syntax.

• Allow empty type parameter lists in certain cases (#​3512)

  TypeScript allows interface declarations and type aliases to have empty type parameter lists. Previously esbuild didn't handle this edge case but with this release, esbuild will now parse this syntax:

  interface Foo<> {}
  type Bar<> = {}

  This fix was contributed by @​magic-akari.

egoist/tsup (tsup)

v8.0.2

Compare Source

Bug Fixes

• support swc target for mjs (#​1081) (83c7c7f)

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

[adaptly-bot]

✅  esbuild

No breaking changes found.

[github-actions]

WASM Size

Engine	This PR	Base branch	Diff
Postgres	2.062MiB	2.062MiB	0.000B
Postgres (gzip)	814.220KiB	814.224KiB	-4.000B
Mysql	2.044MiB	2.044MiB	0.000B
Mysql (gzip)	806.074KiB	806.078KiB	-4.000B
Sqlite	2.005MiB	2.005MiB	0.000B
Sqlite (gzip)	792.460KiB	792.464KiB	-4.000B

[codspeed-hq]

CodSpeed Performance Report

Merging #4580 will not alter performance

_{Comparing renovate/patch-driver-adapters-directory (f2128fb) with main (5a9203d)}

Summary

✅ 11 untouched benchmarks

[github-actions]

✅ WASM query-engine performance won't change substantially (1.001x)

Full benchmark report

DATABASE_URL="postgresql://postgres:postgres@localhost:5432/bench?schema=imdb_bench&sslmode=disable" \
node --experimental-wasm-modules query-engine/driver-adapters/executor/dist/bench.mjs
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
"
cpu: AMD EPYC 7763 64-Core Processor
runtime: node v18.19.0 (x64-linux)

benchmark                   time (avg)             (min … max)       p75       p99      p999
-------------------------------------------------------------- -----------------------------
• movies.findMany() (all - ~50K)
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline     295 ms/iter       (292 ms … 302 ms)    300 ms    302 ms    302 ms
Web Assembly: Latest       377 ms/iter       (375 ms … 382 ms)    381 ms    382 ms    382 ms
Web Assembly: Current      377 ms/iter       (374 ms … 384 ms)    383 ms    384 ms    384 ms
Node API: Current          207 ms/iter       (202 ms … 209 ms)    209 ms    209 ms    209 ms

summary for movies.findMany() (all - ~50K)
  Web Assembly: Current
   1.82x slower than Node API: Current
   1.28x slower than Web Assembly: Baseline
   1x faster than Web Assembly: Latest

• movies.findMany({ take: 2000 })
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline  11'597 µs/iter (11'335 µs … 13'509 µs) 11'587 µs 13'509 µs 13'509 µs
Web Assembly: Latest    15'261 µs/iter (14'896 µs … 17'059 µs) 15'316 µs 17'059 µs 17'059 µs
Web Assembly: Current   15'322 µs/iter (15'085 µs … 16'606 µs) 15'343 µs 16'606 µs 16'606 µs
Node API: Current        8'328 µs/iter  (7'933 µs … 11'559 µs)  8'379 µs 11'559 µs 11'559 µs

summary for movies.findMany({ take: 2000 })
  Web Assembly: Current
   1.84x slower than Node API: Current
   1.32x slower than Web Assembly: Baseline
   1x faster than Web Assembly: Latest

• movies.findMany({ where: {...}, take: 2000 })
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline   1'866 µs/iter   (1'756 µs … 3'067 µs)  1'836 µs  2'665 µs  3'067 µs
Web Assembly: Latest     2'396 µs/iter   (2'302 µs … 3'067 µs)  2'384 µs  2'985 µs  3'067 µs
Web Assembly: Current    2'435 µs/iter   (2'299 µs … 3'818 µs)  2'393 µs  3'767 µs  3'818 µs
Node API: Current        1'390 µs/iter   (1'290 µs … 1'852 µs)  1'406 µs  1'715 µs  1'852 µs

summary for movies.findMany({ where: {...}, take: 2000 })
  Web Assembly: Current
   1.75x slower than Node API: Current
   1.31x slower than Web Assembly: Baseline
   1.02x slower than Web Assembly: Latest

• movies.findMany({ include: { cast: true } take: 2000 }) (m2m)
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline     552 ms/iter       (547 ms … 569 ms)    552 ms    569 ms    569 ms
Web Assembly: Latest       729 ms/iter       (724 ms … 749 ms)    729 ms    749 ms    749 ms
Web Assembly: Current      731 ms/iter       (725 ms … 742 ms)    738 ms    742 ms    742 ms
Node API: Current          458 ms/iter       (446 ms … 472 ms)    469 ms    472 ms    472 ms

summary for movies.findMany({ include: { cast: true } take: 2000 }) (m2m)
  Web Assembly: Current
   1.6x slower than Node API: Current
   1.32x slower than Web Assembly: Baseline
   1x faster than Web Assembly: Latest

• movies.findMany({ where: {...}, include: { cast: true } take: 2000 }) (m2m)
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline  76'553 µs/iter (76'203 µs … 77'134 µs) 76'763 µs 77'134 µs 77'134 µs
Web Assembly: Latest       102 ms/iter       (102 ms … 103 ms)    103 ms    103 ms    103 ms
Web Assembly: Current      103 ms/iter       (102 ms … 103 ms)    103 ms    103 ms    103 ms
Node API: Current       63'084 µs/iter (62'259 µs … 65'168 µs) 63'269 µs 65'168 µs 65'168 µs

summary for movies.findMany({ where: {...}, include: { cast: true } take: 2000 }) (m2m)
  Web Assembly: Current
   1.63x slower than Node API: Current
   1.34x slower than Web Assembly: Baseline
   1x faster than Web Assembly: Latest

• movies.findMany({ take: 2000, include: { cast: { include: { person: true } } } })
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline     977 ms/iter       (967 ms … 992 ms)    987 ms    992 ms    992 ms
Web Assembly: Latest     1'215 ms/iter   (1'207 ms … 1'230 ms)  1'227 ms  1'230 ms  1'230 ms
Web Assembly: Current    1'214 ms/iter   (1'206 ms … 1'233 ms)  1'221 ms  1'233 ms  1'233 ms
Node API: Current          876 ms/iter       (846 ms … 899 ms)    895 ms    899 ms    899 ms

summary for movies.findMany({ take: 2000, include: { cast: { include: { person: true } } } })
  Web Assembly: Current
   1.39x slower than Node API: Current
   1.24x slower than Web Assembly: Baseline
   1x faster than Web Assembly: Latest

• movie.findMany({ where: { ... }, take: 2000, include: { cast: { include: { person: true } } } })
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline     138 ms/iter       (137 ms … 139 ms)    139 ms    139 ms    139 ms
Web Assembly: Latest       172 ms/iter       (170 ms … 177 ms)    174 ms    177 ms    177 ms
Web Assembly: Current      172 ms/iter       (170 ms … 174 ms)    174 ms    174 ms    174 ms
Node API: Current          107 ms/iter       (106 ms … 111 ms)    109 ms    111 ms    111 ms

summary for movie.findMany({ where: { ... }, take: 2000, include: { cast: { include: { person: true } } } })
  Web Assembly: Current
   1.6x slower than Node API: Current
   1.25x slower than Web Assembly: Baseline
   1x faster than Web Assembly: Latest

• movie.findMany({ where: { reviews: { author: { ... } }, take: 100 }) (to-many -> to-one)
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline     871 µs/iter     (813 µs … 1'472 µs)    865 µs  1'342 µs  1'472 µs
Web Assembly: Latest     1'203 µs/iter   (1'122 µs … 2'004 µs)  1'193 µs  1'913 µs  2'004 µs
Web Assembly: Current    1'183 µs/iter   (1'126 µs … 1'837 µs)  1'187 µs  1'643 µs  1'837 µs
Node API: Current          786 µs/iter     (705 µs … 1'204 µs)    800 µs    949 µs  1'204 µs

summary for movie.findMany({ where: { reviews: { author: { ... } }, take: 100 }) (to-many -> to-one)
  Web Assembly: Current
   1.51x slower than Node API: Current
   1.36x slower than Web Assembly: Baseline
   1.02x faster than Web Assembly: Latest

• movie.findMany({ where: { cast: { person: { ... } }, take: 100 }) (m2m -> to-one)
-------------------------------------------------------------- -----------------------------
Web Assembly: Baseline     875 µs/iter     (838 µs … 1'509 µs)    878 µs  1'274 µs  1'509 µs
Web Assembly: Latest     1'173 µs/iter   (1'124 µs … 1'762 µs)  1'180 µs  1'490 µs  1'762 µs
Web Assembly: Current    1'180 µs/iter   (1'128 µs … 1'647 µs)  1'190 µs  1'484 µs  1'647 µs
Node API: Current          765 µs/iter     (703 µs … 1'211 µs)    799 µs    852 µs  1'211 µs

summary for movie.findMany({ where: { cast: { person: { ... } }, take: 100 }) (m2m -> to-one)
  Web Assembly: Current
   1.54x slower than Node API: Current
   1.35x slower than Web Assembly: Baseline
   1.01x slower than Web Assembly: Latest

After changes in f2128fb