bump(deps): update dependency esbuild to ^0.19.6 (#708)

[![Mend Renovate logo
banner](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [esbuild](https://togithub.com/evanw/esbuild) | [`^0.19.5` ->
`^0.19.6`](https://renovatebot.com/diffs/npm/esbuild/0.19.5/0.19.6) |
[![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.19.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/npm/esbuild/0.19.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/npm/esbuild/0.19.5/0.19.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.19.5/0.19.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild (esbuild)</summary>

###
[`v0.19.6`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0196)

[Compare
Source](https://togithub.com/evanw/esbuild/compare/v0.19.5...v0.19.6)

-   Fix a constant folding bug with bigint equality

This release fixes a bug where esbuild incorrectly checked for bigint
equality by checking the equality of the bigint literal text. This is
correct if the bigint doesn't have a radix because bigint literals
without a radix are always in canonical form (since leading zeros are
not allowed). However, this is incorrect if the bigint has a radix (e.g.
`0x123n`) because the canonical form is not enforced when a radix is
present.

    ```js
    // Original code
    console.log(!!0n, !!1n, 123n === 123n)
    console.log(!!0x0n, !!0x1n, 123n === 0x7Bn)

    // Old output
    console.log(false, true, true);
    console.log(true, true, false);

    // New output
    console.log(false, true, true);
    console.log(!!0x0n, !!0x1n, 123n === 0x7Bn);
    ```

-   Add some improvements to the JavaScript minifier

This release adds more cases to the JavaScript minifier, including
support for inlining `String.fromCharCode` and
`String.prototype.charCodeAt` when possible:

    ```js
    // Original code
document.onkeydown = e => e.keyCode === 'A'.charCodeAt(0) &&
console.log(String.fromCharCode(55358, 56768))

    // Old output (with --minify)

document.onkeydown=o=>o.keyCode==="A".charCodeAt(0)&&console.log(String.fromCharCode(55358,56768));

    // New output (with --minify)
    document.onkeydown=o=>o.keyCode===65&&console.log("🧀");
    ```

In addition, immediately-invoked function expressions (IIFEs) that
return a single expression are now inlined when minifying. This makes it
possible to use IIFEs in combination with `@__PURE__` annotations to
annotate arbitrary expressions as side-effect free without the IIFE
wrapper impacting code size. For example:

    ```js
    // Original code
const sideEffectFreeOffset = /* @&#8203;__PURE__ */ (() =>
computeSomething())()
    use(sideEffectFreeOffset)

    // Old output (with --minify)
    const e=(()=>computeSomething())();use(e);

    // New output (with --minify)
    const e=computeSomething();use(e);
    ```

- Automatically prefix the `mask-composite` CSS property for WebKit
([#&#8203;3493](https://togithub.com/evanw/esbuild/issues/3493))

The `mask-composite` property will now be prefixed as
`-webkit-mask-composite` for older WebKit-based browsers. In addition to
prefixing the property name, handling older browsers also requires
rewriting the values since WebKit uses non-standard names for the mask
composite modes:

    ```css
    /* Original code */
    div {
      mask-composite: add, subtract, intersect, exclude;
    }

    /* New output (with --target=chrome100) */
    div {
      -webkit-mask-composite:
        source-over,
        source-out,
        source-in,
        xor;
      mask-composite:
        add,
        subtract,
        intersect,
        exclude;
    }
    ```

- Avoid referencing `this` from JSX elements in derived class
constructors
([#&#8203;3454](https://togithub.com/evanw/esbuild/issues/3454))

When you enable `--jsx=automatic` and `--jsx-dev`, the JSX transform is
supposed to insert `this` as the last argument to the `jsxDEV` function.
I'm not sure exactly why this is and I can't find any specification for
it, but in any case this causes the generated code to crash when you use
a JSX element in a derived class constructor before the call to
`super()` as `this` is not allowed to be accessed at that point. For
example

    ```js
    // Original code
    class ChildComponent extends ParentComponent {
      constructor() {
        super(<div />)
      }
    }

    // Problematic output (with --loader=jsx --jsx=automatic --jsx-dev)
    import { jsxDEV } from "react/jsx-dev-runtime";
    class ChildComponent extends ParentComponent {
      constructor() {
        super(/* @&#8203;__PURE__ */ jsxDEV("div", {}, void 0, false, {
          fileName: "<stdin>",
          lineNumber: 3,
          columnNumber: 15
        }, this)); // The reference to "this" crashes here
      }
    }
    ```

The TypeScript compiler doesn't handle this at all while the Babel
compiler just omits `this` for the entire constructor (even after the
call to `super()`). There seems to be no specification so I can't be
sure that this change doesn't break anything important. But given that
Babel is pretty loose with this and TypeScript doesn't handle this at
all, I'm guessing this value isn't too important. React's blog post
seems to indicate that this value was intended to be used for a
React-specific migration warning at some point, so it could even be that
this value is irrelevant now. Anyway the crash in this case should now
be fixed.

- Allow package subpath imports to map to node built-ins
([#&#8203;3485](https://togithub.com/evanw/esbuild/issues/3485))

You are now able to use a [subpath
import](https://nodejs.org/api/packages.html#subpath-imports) in your
package to resolve to a node built-in module. For example, with a
`package.json` file like this:

    ```json
    {
      "type": "module",
      "imports": {
        "#stream": {
          "node": "stream",
          "default": "./stub.js"
        }
      }
    }
    ```

    You can now import from node's `stream` module like this:

    ```js
    import * as stream from '#stream';
    console.log(Object.keys(stream));
    ```

This will import from node's `stream` module when the platform is `node`
and from `./stub.js` otherwise.

- No longer throw an error when a `Symbol` is missing
([#&#8203;3453](https://togithub.com/evanw/esbuild/issues/3453))

Certain JavaScript syntax features use special properties on the global
`Symbol` object. For example, the asynchronous iteration syntax uses
`Symbol.asyncIterator`. Previously esbuild's generated code for older
browsers required this symbol to be polyfilled. However, starting with
this release esbuild will use
[`Symbol.for()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Symbol/for)
to construct these symbols if they are missing instead of throwing an
error about a missing polyfill. This means your code no longer needs to
include a polyfill for missing symbols as long as your code also uses
`Symbol.for()` for missing symbols.

- Parse upcoming changes to TypeScript syntax
([#&#8203;3490](https://togithub.com/evanw/esbuild/issues/3490),
[#&#8203;3491](https://togithub.com/evanw/esbuild/pull/3491))

With this release, you can now use `from` as the name of a default
type-only import in TypeScript code, as well as `of` as the name of an
`await using` loop iteration variable:

    ```ts
    import type from from 'from'
    for (await using of of of) ;
    ```

This matches similar changes in the TypeScript compiler
([#&#8203;56376](https://togithub.com/microsoft/TypeScript/issues/56376)
and
[#&#8203;55555](https://togithub.com/microsoft/TypeScript/issues/55555))
which will start allowing this syntax in an upcoming version of
TypeScript. Please never actually write code like this.

The type-only import syntax change was contributed by
[@&#8203;magic-akari](https://togithub.com/magic-akari).

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
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.

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

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/levaintech/contented).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy41OS44IiwidXBkYXRlZEluVmVyIjoiMzcuNTkuOCIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

package.json

@@ -20,7 +20,7 @@
     "@types/node": "^18.18.6",
     "@typescript-eslint/eslint-plugin": "^6.11.0",
     "@typescript-eslint/parser": "^6.11.0",
-    "esbuild": "^0.19.5",
+    "esbuild": "^0.19.6",
     "esbuild-jest": "^0.5.0",
     "eslint": "^8.53.0",
     "eslint-config-airbnb-base": "^15.0.0",