Update dependency esbuild to ^0.16.0 (#4)

[![Mend
Renovate](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.15.13` ->
`^0.16.0`](https://renovatebot.com/diffs/npm/esbuild/0.15.13/0.16.1) |
[![age](https://badges.renovateapi.com/packages/npm/esbuild/0.16.1/age-slim)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://badges.renovateapi.com/packages/npm/esbuild/0.16.1/adoption-slim)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://badges.renovateapi.com/packages/npm/esbuild/0.16.1/compatibility-slim/0.15.13)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://badges.renovateapi.com/packages/npm/esbuild/0.16.1/confidence-slim/0.15.13)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>evanw/esbuild</summary>

###
[`v0.16.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;0161)

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

This is a hotfix for the previous release.

- Re-allow importing JSON with the `copy` loader using an import
assertion

The previous release made it so when `assert { type: 'json' }` is
present on an import statement, esbuild validated that the `json` loader
was used. This is what an import assertion is supposed to do. However, I
forgot about the relatively new `copy` loader, which sort of behaves as
if the import path was marked as external (and thus not loaded at all)
except that the file is copied to the output directory and the import
path is rewritten to point to the copy. In this case whatever JavaScript
runtime ends up running the code is the one to evaluate the import
assertion. So esbuild should really allow this case as well. With this
release, esbuild now allows both the `json` and `copy` loaders when an
`assert { type: 'json' }` import assertion is present.

###
[`v0.16.0`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;0160)

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

**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.15.0`. See npm's documentation about
[semver](https://docs.npmjs.com/cli/v6/using-npm/semver/) for more
information.

-   Move all binary executable packages to the `@esbuild/` scope

Binary package executables for esbuild are published as individual
packages separate from the main `esbuild` package so you only have to
download the relevant one for the current platform when you install
esbuild. This release moves all of these packages under the `@esbuild/`
scope to avoid collisions with 3rd-party packages. It also changes them
to a consistent naming scheme that uses the `os` and `cpu` names from
node.

    The package name changes are as follows:

    -   `@esbuild/linux-loong64` => `@esbuild/linux-loong64` (no change)
    -   `esbuild-android-64` => `@esbuild/android-x64`
    -   `esbuild-android-arm64` => `@esbuild/android-arm64`
    -   `esbuild-darwin-64` => `@esbuild/darwin-x64`
    -   `esbuild-darwin-arm64` => `@esbuild/darwin-arm64`
    -   `esbuild-freebsd-64` => `@esbuild/freebsd-x64`
    -   `esbuild-freebsd-arm64` => `@esbuild/freebsd-arm64`
    -   `esbuild-linux-32` => `@esbuild/linux-ia32`
    -   `esbuild-linux-64` => `@esbuild/linux-x64`
    -   `esbuild-linux-arm` => `@esbuild/linux-arm`
    -   `esbuild-linux-arm64` => `@esbuild/linux-arm64`
    -   `esbuild-linux-mips64le` => `@esbuild/linux-mips64el`
    -   `esbuild-linux-ppc64le` => `@esbuild/linux-ppc64`
    -   `esbuild-linux-riscv64` => `@esbuild/linux-riscv64`
    -   `esbuild-linux-s390x` => `@esbuild/linux-s390x`
    -   `esbuild-netbsd-64` => `@esbuild/netbsd-x64`
    -   `esbuild-openbsd-64` => `@esbuild/openbsd-x64`
    -   `esbuild-sunos-64` => `@esbuild/sunos-x64`
    -   `esbuild-wasm` => `esbuild-wasm` (no change)
    -   `esbuild-windows-32` => `@esbuild/win32-ia32`
    -   `esbuild-windows-64` => `@esbuild/win32-x64`
    -   `esbuild-windows-arm64` => `@esbuild/win32-arm64`
    -   `esbuild` => `esbuild` (no change)

Normal usage of the `esbuild` and `esbuild-wasm` packages should not be
affected. These name changes should only affect tools that hard-coded
the individual binary executable package names into custom esbuild
downloader scripts.

This change was not made with performance in mind. But as a bonus,
installing esbuild with npm may potentially happen faster now. This is
because npm's package installation protocol is inefficient: it always
downloads metadata for all past versions of each package even when it
only needs metadata about a single version. This makes npm package
downloads O(n) in the number of published versions, which penalizes
packages like esbuild that are updated regularly. Since most of
esbuild's package names have now changed, npm will now need to download
much less data when installing esbuild (8.72mb of package manifests
before this change → 0.06mb of package manifests after this change).
However, this is only a temporary improvement. Installing esbuild will
gradually get slower again as further versions of esbuild are published.

-   Publish a shell script that downloads esbuild directly

In addition to all of the existing ways to install esbuild, you can now
also download esbuild directly like this:

    ```sh
    curl -fsSL https://esbuild.github.io/dl/latest | sh
    ```

This runs a small shell script that downloads the latest `esbuild`
binary executable to the current directory. This can be convenient on
systems that don't have `npm` installed or when you just want to get a
copy of esbuild quickly without any extra steps. If you want a specific
version of esbuild (starting with this version onward), you can provide
that version in the URL instead of `latest`:

    ```sh
    curl -fsSL https://esbuild.github.io/dl/v0.16.0 | sh
    ```

Note that the download script needs to be able to access
registry.npmjs.org to be able to complete the download. This download
script doesn't yet support all of the platforms that esbuild supports
because I lack the necessary testing environments. If the download
script doesn't work for you because you're on an unsupported platform,
please file an issue on the esbuild repo so we can add support for it.

-   Fix some parameter names for the Go API

This release changes some parameter names for the Go API to be
consistent with the JavaScript and CLI APIs:

    -   `OutExtensions` => `OutExtension`
    -   `JSXMode` => `JSX`

-   Add additional validation of API parameters

The JavaScript API now does some additional validation of API parameters
to catch incorrect uses of esbuild's API. The biggest impact of this is
likely that esbuild now strictly only accepts strings with the `define`
parameter. This would already have been a type error with esbuild's
TypeScript type definitions, but it was previously not enforced for
people using esbuild's API JavaScript without TypeScript.

The `define` parameter appears at first glance to take a JSON object if
you aren't paying close attention, but this actually isn't true. Values
for `define` are instead strings of JavaScript code. This means you have
to use `define: { foo: '"bar"' }` to replace `foo` with the string
`"bar"`. Using `define: { foo: 'bar' }` actually replaces `foo` with the
identifier `bar`. Previously esbuild allowed you to pass `define: { foo:
false }` and `false` was automatically converted into a string, which
made it more confusing to understand what `define` actually represents.
Starting with this release, passing non-string values such as with
`define: { foo: false }` will no longer be allowed. You will now have to
write `define: { foo: 'false' }` instead.

- Generate shorter data URLs if possible
([#&#8203;1843](https://togithub.com/evanw/esbuild/issues/1843))

Loading a file with esbuild's `dataurl` loader generates a JavaScript
module with a [data
URL](https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/Data_URLs)
for that file in a string as a single default export. Previously the
data URLs generated by esbuild all used [base64
encoding](https://en.wikipedia.org/wiki/Base64). However, this is
unnecessarily long for most textual data (e.g. SVG images). So with this
release, esbuild's `dataurl` loader will now use percent encoding
instead of base64 encoding if the result will be shorter. This can
result in ~25% smaller data URLs for large SVGs. If you want the old
behavior, you can use the `base64` loader instead and then construct the
data URL yourself.

- Avoid marking entry points as external
([#&#8203;2382](https://togithub.com/evanw/esbuild/issues/2382))

Previously you couldn't specify `--external:*` to mark all import paths
as external because that also ended up making the entry point itself
external, which caused the build to fail. With this release, esbuild's
`external` API parameter no longer applies to entry points so using
`--external:*` is now possible.

One additional consequence of this change is that the `kind` parameter
is now required when calling the `resolve()` function in esbuild's
plugin API. Previously the `kind` parameter defaulted to `entry-point`,
but that no longer interacts with `external` so it didn't seem wise for
this to continue to be the default. You now have to specify `kind` so
that the path resolution mode is explicit.

- Disallow non-`default` imports when `assert { type: 'json' }` is
present

There is now standard behavior for importing a JSON file into an ES
module using an `import` statement. However, it requires you to place
the `assert { type: 'json' }` import assertion after the import path.
This import assertion tells the JavaScript runtime to throw an error if
the import does not end up resolving to a JSON file. On the web, the
type of a file is determined by the `Content-Type` HTTP header instead
of by the file extension. The import assertion prevents security
problems on the web where a `.json` file may actually resolve to a
JavaScript file containing malicious code, which is likely not expected
for an import that is supposed to only contain pure side-effect free
data.

By default, esbuild uses the file extension to determine the type of a
file, so this import assertion is unnecessary with esbuild. However,
esbuild's JSON import feature has a non-standard extension that allows
you to import top-level properties of the JSON object as named imports.
For example, esbuild lets you do this:

    ```js
    import { version } from './package.json'
    ```

This is useful for tree-shaking when bundling because it means esbuild
will only include the the `version` field of `package.json` in your
bundle. This is non-standard behavior though and doesn't match the
behavior of what happens when you import JSON in a real JavaScript
runtime (after adding `assert { type: 'json' }`). In a real JavaScript
runtime the only thing you can import is the `default` import. So with
this release, esbuild will now prevent you from importing non-`default`
import names if `assert { type: 'json' }` is present. This ensures that
code containing `assert { type: 'json' }` isn't relying on non-standard
behavior that won't work everywhere. So the following code is now an
error with esbuild when bundling:

    ```js
    import { version } from './package.json' assert { type: 'json' }
    ```

In addition, adding `assert { type: 'json' }` to an import statement now
means esbuild will generate an error if the loader for the file is
anything other than `json`, which is required by the import assertion
specification.

- Provide a way to disable automatic escaping of `</script>`
([#&#8203;2649](https://togithub.com/evanw/esbuild/issues/2649))

If you inject esbuild's output into a script tag in an HTML file, code
containing the literal characters `</script>` will cause the tag to be
ended early which will break the code:

    ```html
    <script>
      console.log("</script>");
    </script>
    ```

To avoid this, esbuild automatically escapes these strings in generated
JavaScript files (e.g. `"</script>"` becomes `"<\/script>"` instead).
This also applies to `</style>` in generated CSS files. Previously this
always happened and there wasn't a way to turn this off.

With this release, esbuild will now only do this if the `platform`
setting is set to `browser` (the default value). Setting `platform` to
`node` or `neutral` will disable this behavior. This behavior can also
now be disabled with `--supported:inline-script=false` (for JS) and
`--supported:inline-style=false` (for CSS).

- Throw an early error if decoded UTF-8 text isn't a `Uint8Array`
([#&#8203;2532](https://togithub.com/evanw/esbuild/issues/2532))

If you run esbuild's JavaScript API in a broken JavaScript environment
where `new TextEncoder().encode("") instanceof Uint8Array` is false,
then esbuild's API will fail with a confusing serialization error
message that makes it seem like esbuild has a bug even though the real
problem is that the JavaScript environment itself is broken. This can
happen when using the test framework called [Jest](https://jestjs.io/).
With this release, esbuild's API will now throw earlier when it detects
that the environment is unable to encode UTF-8 text correctly with an
error message that makes it more clear that this is not a problem with
esbuild.

-   Change the default "legal comment" behavior

The legal comments feature automatically gathers comments containing
`@license` or `@preserve` and puts the comments somewhere (either in the
generated code or in a separate file). People sometimes want this to
happen so that the their dependencies' software licenses are retained in
the generated output code. By default esbuild puts these comments at the
end of the file when bundling. However, people sometimes find this
confusing because these comments can be very generic and may not mention
which library they come from. So with this release, esbuild will now
discard legal comments by default. You now have to opt-in to preserving
them if you want this behavior.

- Enable the `module` condition by default
([#&#8203;2417](https://togithub.com/evanw/esbuild/issues/2417))

Package authors want to be able to use the new
[`exports`](https://nodejs.org/api/packages.html#conditional-exports)
field in `package.json` to provide tree-shakable ESM code for ESM-aware
bundlers while simultaneously providing fallback CommonJS code for other
cases.

Node's proposed way to do this involves using the `import` and `require`
export conditions so that you get the ESM code if you use an import
statement and the CommonJS code if you use a require call. However, this
has a major drawback: if some code in the bundle uses an import
statement and other code in the bundle uses a require call, then you'll
get two copies of the same package in the bundle. This is known as the
[dual package
hazard](https://nodejs.org/api/packages.html#dual-package-hazard) and
can lead to bloated bundles or even worse to subtle logic bugs.

Webpack supports an alternate solution: an export condition called
`module` that takes effect regardless of whether the package was
imported using an import statement or a require call. This works because
bundlers such as Webpack support importing a ESM using a require call
(something node doesn't support). You could already do this with esbuild
using `--conditions=module` but you previously had to explicitly enable
this. Package authors are concerned that esbuild users won't know to do
this and will get suboptimal output with their package, so they have
requested for esbuild to do this automatically.

So with this release, esbuild will now automatically add the `module`
condition when there aren't any custom `conditions` already configured.
You can disable this with `--conditions=` or `conditions: []` (i.e.
explicitly clearing all custom conditions).

-   Rename the `master` branch to `main`

The primary branch for this repository was previously called `master`
but is now called `main`. This change mirrors a similar change in many
other projects.

- Remove esbuild's `_exit(0)` hack for WebAssembly
([#&#8203;714](https://togithub.com/evanw/esbuild/issues/714))

Node had an unfortunate bug where the node process is unnecessarily kept
open while a WebAssembly module is being optimized:
[https://github.com/nodejs/node/issues/36616](https://togithub.com/nodejs/node/issues/36616).
This means cases where running `esbuild` should take a few milliseconds
can end up taking many seconds instead.

The workaround was to force node to exit by ending the process early.
This was done by esbuild in one of two ways depending on the exit code.
For non-zero exit codes (i.e. when there is a build error), the
`esbuild` command could just call `process.kill(process.pid)` to avoid
the hang. But for zero exit codes, esbuild had to load a N-API native
node extension that calls the operating system's `exit(0)` function.

However, this problem has essentially been fixed in node starting with
version 18.3.0. So I have removed this hack from esbuild. If you are
using an earlier version of node with `esbuild-wasm` and you don't want
the `esbuild` command to hang for a while when exiting, you can upgrade
to node 18.3.0 or higher to remove the hang.

The fix came from a V8 upgrade: [this
commit](https://togithub.com/v8/v8/commit/bfe12807c14c91714c7db1485e6b265439375e16)
enabled [dynamic tiering for
WebAssembly](https://v8.dev/blog/wasm-dynamic-tiering) by default for
all projects that use V8's WebAssembly implementation. Previously all
functions in the WebAssembly module were optimized in a single batch job
but with dynamic tiering, V8 now optimizes individual WebAssembly
functions as needed. This avoids unnecessary WebAssembly compilation
which allows node to exit on time.

###
[`v0.15.18`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;01518)

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

-   Performance improvements for both JS and CSS

This release brings noticeable performance improvements for JS parsing
and for CSS parsing and printing. Here's an example benchmark for using
esbuild to pretty-print a single large minified CSS file and JS file:

    | Test case      | Previous release | This release       |
    |----------------|------------------|--------------------|
    | 4.8mb CSS file | 19ms             | 11ms (1.7x faster) |
    | 5.8mb JS file  | 36ms             | 32ms (1.1x faster) |

    The performance improvements were very straightforward:

- Identifiers were being scanned using a generic character advancement
function instead of using custom inline code. Advancing past each
character involved UTF-8 decoding as well as updating multiple member
variables. This was sped up using loop that skips UTF-8 decoding
entirely and that only updates member variables once at the end. This is
faster because identifiers are plain ASCII in the vast majority of
cases, so Unicode decoding is almost always unnecessary.

- CSS identifiers and CSS strings were still being printed one character
at a time. Apparently I forgot to move this part of esbuild's CSS
infrastructure beyond the proof-of-concept stage. These were both very
obvious in the profiler, so I think maybe I have just never profiled
esbuild's CSS printing before?

- There was unnecessary work being done that was related to source maps
when source map output was disabled. I likely haven't observed this
before because esbuild's benchmarks always have source maps enabled.
This work is now disabled when it's not going to be used.

I definitely should have caught these performance issues earlier. Better
late than never I suppose.

###
[`v0.15.17`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;01517)

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

- Search for missing source map code on the file system
([#&#8203;2711](https://togithub.com/evanw/esbuild/issues/2711))

[Source maps](https://sourcemaps.info/spec.html) are JSON files that map
from compiled code back to the original code. They provide the original
source code using two arrays: `sources` (required) and `sourcesContent`
(optional). When bundling is enabled, esbuild is able to bundle code
with source maps that was compiled by other tools (e.g. with Webpack)
and emit source maps that map all the way back to the original code
(e.g. before Webpack compiled it).

Previously if the input source maps omitted the optional
`sourcesContent` array, esbuild would use `null` for the source content
in the source map that it generates (since the source content isn't
available). However, sometimes the original source code is actually
still present on the file system. With this release, esbuild will now
try to find the original source code using the path in the `sources`
array and will use that instead of `null` if it was found.

- Fix parsing bug with TypeScript `infer` and `extends`
([#&#8203;2712](https://togithub.com/evanw/esbuild/issues/2712))

This release fixes a bug where esbuild incorrectly failed to parse valid
TypeScript code that nests `extends` inside `infer` inside `extends`,
such as in the example below:

    ```ts
    type A<T> = {};
    type B = {} extends infer T extends {} ? A<T> : never;
    ```

    TypeScript code that does this should now be parsed correctly.

- Use `WebAssembly.instantiateStreaming` if available
([#&#8203;1036](https://togithub.com/evanw/esbuild/pull/1036),
[#&#8203;1900](https://togithub.com/evanw/esbuild/pull/1900))

Currently the WebAssembly version of esbuild uses `fetch` to download
`esbuild.wasm` and then `WebAssembly.instantiate` to compile it. There
is a newer API called `WebAssembly.instantiateStreaming` that both
downloads and compiles at the same time, which can be a performance
improvement if both downloading and compiling are slow. With this
release, esbuild now attempts to use `WebAssembly.instantiateStreaming`
and falls back to the original approach if that fails.

The implementation for this builds on a PR by
[@&#8203;lbwa](https://togithub.com/lbwa).

- Preserve Webpack comments inside constructor calls
([#&#8203;2439](https://togithub.com/evanw/esbuild/issues/2439))

This improves the use of esbuild as a faster TypeScript-to-JavaScript
frontend for Webpack, which has special [magic
comments](https://webpack.js.org/api/module-methods/#magic-comments)
inside `new Worker()` expressions that affect Webpack's behavior.

###
[`v0.15.16`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;01516)

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

- Add a package alias feature
([#&#8203;2191](https://togithub.com/evanw/esbuild/issues/2191))

With this release, you can now easily substitute one package for another
at build time with the new `alias` feature. For example,
`--alias:oldpkg=newpkg` replaces all imports of `oldpkg` with `newpkg`.
One use case for this is easily replacing a node-only package with a
browser-friendly package in 3rd-party code that you don't control. These
new substitutions happen first before all of esbuild's existing path
resolution logic.

Note that when an import path is substituted using an alias, the
resulting import path is resolved in the working directory instead of in
the directory containing the source file with the import path. If
needed, the working directory can be set with the `cd` command when
using the CLI or with the `absWorkingDir` setting when using the JS or
Go APIs.

- Fix crash when pretty-printing minified JSX with object spread of
object literal with computed property
([#&#8203;2697](https://togithub.com/evanw/esbuild/issues/2697))

JSX elements are translated to JavaScript function calls and JSX element
attributes are translated to properties on a JavaScript object literal.
These properties are always either strings (e.g. in `<x y />`, `y` is a
string) or an object spread (e.g. in `<x {...y} />`, `y` is an object
spread) because JSX doesn't provide syntax for directly passing a
computed property as a JSX attribute. However, esbuild's minifier has a
rule that tries to inline object spread with an inline object literal in
JavaScript. For example, `x = { ...{ y } }` is minified to `x={y}` when
minification is enabled. This means that there is a way to generate a
non-string non-spread JSX attribute in esbuild's internal
representation. One example is with `<x {...{ [y]: z }} />`. When
minification is enabled, esbuild's internal representation of this is
something like `<x [y]={z} />` due to object spread inlining, which is
not valid JSX syntax. If this internal representation is then
pretty-printed as JSX using `--minify --jsx=preserve`, esbuild
previously crashed when trying to print this invalid syntax. With this
release, esbuild will now print `<x {...{[y]:z}}/>` in this scenario
instead of crashing.

###
[`v0.15.15`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;01515)

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

- Remove duplicate CSS rules across files
([#&#8203;2688](https://togithub.com/evanw/esbuild/issues/2688))

When two or more CSS rules are exactly the same (even if they are not
adjacent), all but the last one can safely be removed:

    ```css
    /* Before */
    a { color: red; }
    span { font-weight: bold; }
    a { color: red; }

    /* After */
    span { font-weight: bold; }
    a { color: red; }
    ```

Previously esbuild only did this transformation within a single source
file. But with this release, esbuild will now do this transformation
across source files, which may lead to smaller CSS output if the same
rules are repeated across multiple CSS source files in the same bundle.
This transformation is only enabled when minifying (specifically when
syntax minification is enabled).

- Add `deno` as a valid value for `target`
([#&#8203;2686](https://togithub.com/evanw/esbuild/issues/2686))

The `target` setting in esbuild allows you to enable or disable
JavaScript syntax features for a given version of a set of target
JavaScript VMs. Previously [Deno](https://deno.land/) was not one of the
JavaScript VMs that esbuild supported with `target`, but it will now be
supported starting from this release. For example, versions of Deno
older than v1.2 don't support the new `||=` operator, so adding e.g.
`--target=deno1.0` to esbuild now lets you tell esbuild to transpile
`||=` to older JavaScript.

- Fix the `esbuild-wasm` package in Node v19
([#&#8203;2683](https://togithub.com/evanw/esbuild/issues/2683))

A recent change to Node v19 added a non-writable `crypto` property to
the global object:
[https://github.com/nodejs/node/pull/44897](https://togithub.com/nodejs/node/pull/44897).
This conflicts with Go's WebAssembly shim code, which overwrites the
global `crypto` property. As a result, all Go-based WebAssembly code
that uses the built-in shim (including esbuild) is now broken on Node
v19. This release of esbuild fixes the issue by reconfiguring the global
`crypto` property to be writable before invoking Go's WebAssembly shim
code.

- Fix CSS dimension printing exponent confusion edge case
([#&#8203;2677](https://togithub.com/evanw/esbuild/issues/2677))

In CSS, a dimension token has a numeric "value" part and an identifier
"unit" part. For example, the dimension token `32px` has a value of `32`
and a unit of `px`. The unit can be any valid CSS identifier. The value
can be any number in floating-point format including an optional
exponent (e.g. `-3.14e-0` has an exponent of `e-0`). The full details of
this syntax are here: https://www.w3.org/TR/css-syntax-3/.

To maintain the integrity of the dimension token through the printing
process, esbuild must handle the edge case where the unit looks like an
exponent. One such case is the dimension `1e\32` which has the value `1`
and the unit `e2`. It would be bad if this dimension token was printed
such that a CSS parser would parse it as a number token with the value
`1e2` instead of a dimension token. The way esbuild currently does this
is to escape the leading `e` in the dimension unit, so esbuild would
parse `1e\32` but print `1\65 2` (both `1e\32` and `1\65 2` represent a
dimension token with a value of `1` and a unit of `e2`).

However, there is an even narrower edge case regarding this edge case.
If the value part of the dimension token itself has an `e`, then it's
not necessary to escape the `e` in the dimension unit because a CSS
parser won't confuse the unit with the exponent even though it looks
like one (since a number can only have at most one exponent). This came
up because the grammar for the CSS `unicode-range` property uses a hack
that lets you specify a hexadecimal range without quotes even though CSS
has no token for a hexadecimal range. The hack is to allow the
hexadecimal range to be parsed as a dimension token and optionally also
a number token. Here is the grammar for `unicode-range`:

        unicode-range =
          <urange>#

        <urange> =
          u '+' <ident-token> '?'*            |
          u <dimension-token> '?'*            |
          u <number-token> '?'*               |
          u <number-token> <dimension-token>  |
          u <number-token> <number-token>     |
          u '+' '?'+

and here is an example `unicode-range` declaration that was problematic
for esbuild:

    ```css
    @&#8203;font-face {
      unicode-range: U+0e2e-0e2f;
    }
    ```

This is parsed as a dimension with a value of `+0e2` and a unit of
`e-0e2f`. This was problematic for esbuild because the unit starts with
`e-0` which could be confused with an exponent when appended after a
number, so esbuild was escaping the `e` character in the unit. However,
this escaping is unnecessary because in this case the dimension value
already has an exponent in it. With this release, esbuild will no longer
unnecessarily escape the `e` in the dimension unit in these cases, which
should fix the printing of `unicode-range` declarations.

An aside: You may be wondering why esbuild is trying to escape the `e`
at all and why it doesn't just pass through the original source code
unmodified. The reason why esbuild does this is that, for robustness,
esbuild's AST generally tries to omit semantically-unrelated information
and esbuild's code printers always try to preserve the semantics of the
underlying AST. That way the rest of esbuild's internals can just deal
with semantics instead of presentation. They don't have to think about
how the AST will be printed when changing the AST. This is the same
reason that esbuild's JavaScript AST doesn't have a "parentheses" node
(e.g. `a * (b + c)` is represented by the AST `multiply(a, add(b, c))`
instead of `multiply(a, parentheses(add(b, c)))`). Instead, the printer
automatically inserts parentheses as necessary to maintain the semantics
of the AST, which means all of the optimizations that run over the AST
don't have to worry about keeping the parentheses up to date. Similarly,
the CSS AST for the dimension token stores the actual unit and the
printer makes sure the unit is properly escaped depending on what value
it's placed after. All of the other code operating on CSS ASTs doesn't
have to worry about parsing escapes to compare units or about keeping
escapes up to date when the AST is modified. Hopefully that makes sense.

- Attempt to avoid creating the `node_modules/.cache` directory for
people that use Yarn 2+ in Plug'n'Play mode
([#&#8203;2685](https://togithub.com/evanw/esbuild/issues/2685))

When Yarn's PnP mode is enabled, packages installed by Yarn may or may
not be put inside `.zip` files. The specific heuristics for when this
happens change over time in between Yarn versions. This is problematic
for esbuild because esbuild's JavaScript package needs to execute a
binary file inside the package. Yarn makes extensive modifications to
Node's file system APIs at run time to pretend that `.zip` files are
normal directories and to make it hard to tell whether a file is real or
not (since in theory it doesn't matter). But they haven't modified
Node's `child_process.execFileSync` API so attempting to execute a file
inside a zip file fails. To get around this, esbuild previously used
Node's file system APIs to copy the binary executable to another
location before invoking `execFileSync`. Under the hood this caused Yarn
to extract the file from the zip file into a real file that can then be
run.

However, esbuild copied its executable into
`node_modules/.cache/esbuild`. This is the [official recommendation from
the Yarn
team](https://yarnpkg.com/advanced/rulebook/#packages-should-never-write-inside-their-own-folder-outside-of-postinstall)
for where packages are supposed to put these types of files when Yarn
PnP is being used. However, users of Yarn PnP with esbuild find this
really annoying because they don't like looking at the `node_modules`
directory. With this release, esbuild now sets `"preferUnplugged": true`
in its `package.json` files, which tells newer versions of Yarn to not
put esbuild's packages in a zip file. There may exist older versions of
Yarn that don't support `preferUnplugged`. In that case esbuild should
still copy the executable to a cache directory, so it should still run
(hopefully, since I haven't tested this myself). Note that esbuild
setting `"preferUnplugged": true` may have the side effect of esbuild
taking up more space on the file system in the event that multiple
platforms are installed simultaneously, or that you're using an older
version of Yarn that always installs packages for all platforms. In that
case you may want to update to a newer version of Yarn since Yarn has
recently changed to only install packages for the current platform.

###
[`v0.15.14`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#&#8203;01514)

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

- Fix parsing of TypeScript `infer` inside a conditional `extends`
([#&#8203;2675](https://togithub.com/evanw/esbuild/issues/2675))

Unlike JavaScript, parsing TypeScript sometimes requires backtracking.
The `infer A` type operator can take an optional constraint of the form
`infer A extends B`. However, this syntax conflicts with the similar
conditional type operator `A extends B ? C : D` in cases where the
syntax is combined, such as `infer A extends B ? C : D`. This is
supposed to be parsed as `(infer A) extends B ? C : D`. Previously
esbuild incorrectly parsed this as `(infer A extends B) ? C : D`
instead, which is a parse error since the `?:` conditional operator
requires the `extends` keyword as part of the conditional type.
TypeScript disambiguates by speculatively parsing the `extends` after
the `infer`, but backtracking if a `?` token is encountered afterward.
With this release, esbuild should now do the same thing, so esbuild
should now correctly parse these types. Here's a real-world example of
such a type:

    ```ts
type Normalized<T> = T extends Array<infer A extends object ? infer A :
never>
      ? Dictionary<Normalized<A>>
      : {
[P in keyof T]: T[P] extends Array<infer A extends object ? infer A :
never>
            ? Dictionary<Normalized<A>>
            : Normalized<T[P]>
        }
    ```

- Avoid unnecessary watch mode rebuilds when debug logging is enabled
([#&#8203;2661](https://togithub.com/evanw/esbuild/issues/2661))

When debug-level logs are enabled (such as with `--log-level=debug`),
esbuild's path resolution subsystem generates debug log messages that
say something like "Read 20 entries for directory /home/user" to help
you debug what esbuild's path resolution is doing. This caused esbuild's
watch mode subsystem to add a dependency on the full list of entries in
that directory since if that changes, the generated log message would
also have to be updated. However, meant that on systems where a parent
directory undergoes constant directory entry churn, esbuild's watch mode
would continue to rebuild if `--log-level=debug` was passed.

With this release, these debug log messages are now generated by
"peeking" at the file system state while bypassing esbuild's watch mode
dependency tracking. So now watch mode doesn't consider the count of
directory entries in these debug log messages to be a part of the build
that needs to be kept up to date when the file system state changes.

</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://app.renovatebot.com/dashboard#github/ajvpot/lockfileparsergo).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC40OS4wIiwidXBkYXRlZEluVmVyIjoiMzQuNDkuMCJ9-->

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

Author: renovate[bot]

js/dist/built.js

@@ -14,7 +14,7 @@
     "node-stdlib-browser": "^1.2.0"
   },
   "devDependencies": {
-    "esbuild": "^0.15.13",
+    "esbuild": "^0.16.0",
     "prettier": "^2.7.1"
   }
 }

js/package.json

@@ -9,15 +9,115 @@
   dependencies:
     grapheme-splitter "^1.0.4"
 
-"@esbuild/[email protected]":
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/@esbuild/android-arm/-/android-arm-0.15.13.tgz#ce11237a13ee76d5eae3908e47ba4ddd380af86a"
-  integrity sha512-RY2fVI8O0iFUNvZirXaQ1vMvK0xhCcl0gqRj74Z6yEiO1zAUa7hbsdwZM1kzqbxHK7LFyMizipfXT3JME+12Hw==
-
-"@esbuild/[email protected]":
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/@esbuild/linux-loong64/-/linux-loong64-0.15.13.tgz#64e8825bf0ce769dac94ee39d92ebe6272020dfc"
-  integrity sha512-+BoyIm4I8uJmH/QDIH0fu7MG0AEx9OXEDXnqptXCwKOlOqZiS4iraH1Nr7/ObLMokW3sOCeBNyD68ATcV9b9Ag==
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/android-arm64/-/android-arm64-0.16.1.tgz#3843eb0ae218a7139d5c6eccfea8d65cef4c54f3"
+  integrity sha512-BHOqlxpx2UNDHvn6Ldu2QftJXYtXmsagaECew1RiY27hd/wqCx+pz5ByQpNRPyqv5S9uODqtk69LkXpmPqSqJA==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/android-arm/-/android-arm-0.16.1.tgz#5cc3f277b0c853da9d6241f8024da6a7bf6964b9"
+  integrity sha512-zkalq3i2M+l812fhSswRM9FSryXEmoz30bfDlPYOl1ij0hBZd+lU3rRUzHSenU8LpsN/SAgX1d/mwq2dvGO3Qw==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/android-x64/-/android-x64-0.16.1.tgz#8d8cddad9accf599518207b03ee4a17d23caf250"
+  integrity sha512-/xaEo77WGtykr4+VUHZF78xc/pfmtrfpYb6tJjA5sPCsqynXKdM7Z1E7LoqP7NJZbf5KW8Klm64f9CTIm97R9w==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/darwin-arm64/-/darwin-arm64-0.16.1.tgz#03e64371d018a90c2d25ffb5f743e78d7ee29098"
+  integrity sha512-vYWHFDhxF4hmOVs1NkanPtbBb2ZcVAkMJan5iImpaL/FA2SfYIFX8IN/W20e7/2DpDxd7XkrP1i5bQUAsyXjsQ==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/darwin-x64/-/darwin-x64-0.16.1.tgz#9036cf2c6d796cf6040693c77e7343d2cc37fbed"
+  integrity sha512-UFJ8swS3ZiQgT51ll9P3K+WOiYSc3Dw68kbZqXlmF5zwB7p/nx31jilW6ie+UlKIFRw4X0Z1SejwVC6ZpH7PSQ==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/freebsd-arm64/-/freebsd-arm64-0.16.1.tgz#bc3e33c46af0eea93ee0c4bbb37dd41bf9548711"
+  integrity sha512-/6kJ0VROu7JYiWMV9EscVHH66HCCDd0Uo3mGjrP6vtscF19f9Prkf3xZJH3AO9OxUOZpfjtZatf9b0OyKVMl6A==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/freebsd-x64/-/freebsd-x64-0.16.1.tgz#48fba6c63463409452ebc8544139e091b7797afb"
+  integrity sha512-BKYAYhsgD/6/mOeOwMSEcTyL9GlFBNr2LkgWEaugUp/oXCC+ScCH/EqphD3Jp5MsMNIk71b0YqDDveDHXuwcLw==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-arm64/-/linux-arm64-0.16.1.tgz#b2275692feeb7b6f42d8eb25ddf1c96a0378b586"
+  integrity sha512-3mRaXF3nVjgPcrJOLr3IdidMLolHi3nMO7UQPYX+asKqn3UVnNqD30vlZvg8r1amJ7o5TOHvPXqgHK33ivyMPg==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-arm/-/linux-arm-0.16.1.tgz#a54ac0c0f69b504134fbe7f173a66432f54331aa"
+  integrity sha512-ZKBI/JEIjcG9YbERCDR1qPBVjr47+BKGp32Iz2cf00001yhF8mGPhVJse69jR3Wb1RU78BijVKhHPvZewsvAKA==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-ia32/-/linux-ia32-0.16.1.tgz#e34635e929c17ff4f3cadcec656813574a654ef9"
+  integrity sha512-rTiIs5ms38XUb5Bn7hbbkR45CS3rz/hC/IfRE8Uccgzo4qRkf3Zd0Re6IUoCP+DvcTzLPz1VLfDO8VyD7UUI0w==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-loong64/-/linux-loong64-0.16.1.tgz#b9382c5e3e0640e093a18f42680e87ac0f79094b"
+  integrity sha512-TgUV9ZpMzo9O48AkwJfgx9HJIMnA9kCopAYmjp2y9TPT6Z7Crxrlp2XVkaZ2mxhvrrzVsHlhwfolcj1scXHfKw==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-mips64el/-/linux-mips64el-0.16.1.tgz#9b5ecec04f308d7e9951cd11bad607ced1b25ab5"
+  integrity sha512-TH6aEzbImbo1iUrdhtRdhgynuuiODx+Ju2DaIq+eUIOLj6Hg47NlcM5hQ3bHVKxflPiGIrGi1DTacrEoQOiOTg==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-ppc64/-/linux-ppc64-0.16.1.tgz#8af2ab35166ff56bcabb2094e956d12b261db321"
+  integrity sha512-//BU2o/gfw6clxJCrU8xa0gxElP18HiAzS/pN1HKzL2ayqz8WinOYEzPOZrqJvkC4u2Qoh5NEiVd98wTr2C9eg==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-riscv64/-/linux-riscv64-0.16.1.tgz#a037d507ad99128c75c835db42aa5bf5ed1a5a3e"
+  integrity sha512-pBrrjLBwmlsMR7iNi+W/q5JtfyzlZ97WUxBztZvsGnWBpnmjjgbdPBlwxYbgQAzqzMAsP45j6CJUpGra3SSFiQ==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-s390x/-/linux-s390x-0.16.1.tgz#9700a2595de1363c60723810a88c83f6aec24006"
+  integrity sha512-e4txkDfouCcByJacawPh9M6qmF9TyzJ+Y6Sj4L+Iu7pRBaAldSqI/pQym26XBcawVlmyYhLA51JXVlQdyj3Rlg==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/linux-x64/-/linux-x64-0.16.1.tgz#113cb7634aeed6da9c8edef43df0f0266edaf5d4"
+  integrity sha512-2kSF6dFTN5HbSgA+htdS69npthoR/FDr8PXc9O6h6RqRN+l7y3u8MlFMu9RSsOOD11FigiBJnzUYcl3QRT9eSA==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/netbsd-x64/-/netbsd-x64-0.16.1.tgz#77ae84d4674d6c315a4b652ccbb27ce8e9484dcd"
+  integrity sha512-OkDgqg+drkSEvNOAEPUQrv3g7OlE0hMsLe7on5+GePZvjgQepQ7fQ8T6RGj2nEMGa5Am2Q3jWEVx5lq6bsFpRw==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/openbsd-x64/-/openbsd-x64-0.16.1.tgz#5401d9199efb469ad6f37fdfcaefd16cb2176fd3"
+  integrity sha512-YqC0KN4nJoDSIaBVkUYa1FvreYFKu6wOoWGl+lYmcRzw6pj5f96+WSE7+vRiucKpDd52P1CYlnO9yGzSo9eXSw==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/sunos-x64/-/sunos-x64-0.16.1.tgz#c8d84eb61f66d3811051b9b5c4b63e9ee126217c"
+  integrity sha512-KgfRBLjr6W9iyLLAOU58lSJ7/6W7H+KoDV27CGpEv0R5xR2LYMAE2SQ2sE0r2CP1rDa/huu/Uj1RvcVZ5nptqg==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/win32-arm64/-/win32-arm64-0.16.1.tgz#4b63fdc90349053deaea6c3159837b85f7d73417"
+  integrity sha512-UuKMH583a6epN+L6VxbXwYQ/RISJsz8NN05QlV2l0LY8aV79Wty23BkBz0WF5kOK22eXNavgb2sgcZer6Qg+KA==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/win32-ia32/-/win32-ia32-0.16.1.tgz#1c6c88fb57c426d03bc1fd96461eb0f2e596fc4f"
+  integrity sha512-tnno7oPwPfZAyxRguqTi6ehf/s/x8xq1QtB8TLAfSP3DfIaO1U3gHAf5I/AMVlZPMzwtDUvURRfJK/a72cHyZg==
+
+"@esbuild/[email protected]":
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/@esbuild/win32-x64/-/win32-x64-0.16.1.tgz#ca4024c5fa8bbf32cf586fd1e201d26720becc71"
+  integrity sha512-vxkjnTk2nCxx3eIolisfjvIN0eZj8vp27iF/fh3vQ7GXkEdK/VzbolT8Nl5YsEddrXc5RRJbHulHM0pGuY+VgQ==
 
 "@nodelib/[email protected]":
   version "2.1.5"
@@ -680,133 +780,33 @@ es6-object-assign@^1.1.0:
   resolved "https://registry.yarnpkg.com/es6-object-assign/-/es6-object-assign-1.1.0.tgz#c2c3582656247c39ea107cb1e6652b6f9f24523c"
   integrity sha512-MEl9uirslVwqQU369iHNWZXsI8yaZYGg/D65aOgZkeyFJwHYSxilf7rQzXKI7DdDuBPrBXbfk3sl9hJhmd5AUw==
 
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-android-64/-/esbuild-android-64-0.15.13.tgz#5f25864055dbd62e250f360b38b4c382224063af"
-  integrity sha512-yRorukXBlokwTip+Sy4MYskLhJsO0Kn0/Fj43s1krVblfwP+hMD37a4Wmg139GEsMLl+vh8WXp2mq/cTA9J97g==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-android-arm64/-/esbuild-android-arm64-0.15.13.tgz#d8820f999314efbe8e0f050653a99ff2da632b0f"
-  integrity sha512-TKzyymLD6PiVeyYa4c5wdPw87BeAiTXNtK6amWUcXZxkV51gOk5u5qzmDaYSwiWeecSNHamFsaFjLoi32QR5/w==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-darwin-64/-/esbuild-darwin-64-0.15.13.tgz#99ae7fdaa43947b06cd9d1a1c3c2c9f245d81fd0"
-  integrity sha512-WAx7c2DaOS6CrRcoYCgXgkXDliLnFv3pQLV6GeW1YcGEZq2Gnl8s9Pg7ahValZkpOa0iE/ojRVQ87sbUhF1Cbg==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-darwin-arm64/-/esbuild-darwin-arm64-0.15.13.tgz#bafa1814354ad1a47adcad73de416130ef7f55e3"
-  integrity sha512-U6jFsPfSSxC3V1CLiQqwvDuj3GGrtQNB3P3nNC3+q99EKf94UGpsG9l4CQ83zBs1NHrk1rtCSYT0+KfK5LsD8A==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-freebsd-64/-/esbuild-freebsd-64-0.15.13.tgz#84ef85535c5cc38b627d1c5115623b088d1de161"
-  integrity sha512-whItJgDiOXaDG/idy75qqevIpZjnReZkMGCgQaBWZuKHoElDJC1rh7MpoUgupMcdfOd+PgdEwNQW9DAE6i8wyA==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-freebsd-arm64/-/esbuild-freebsd-arm64-0.15.13.tgz#033f21de434ec8e0c478054b119af8056763c2d8"
-  integrity sha512-6pCSWt8mLUbPtygv7cufV0sZLeylaMwS5Fznj6Rsx9G2AJJsAjQ9ifA+0rQEIg7DwJmi9it+WjzNTEAzzdoM3Q==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-linux-32/-/esbuild-linux-32-0.15.13.tgz#54290ea8035cba0faf1791ce9ae6693005512535"
-  integrity sha512-VbZdWOEdrJiYApm2kkxoTOgsoCO1krBZ3quHdYk3g3ivWaMwNIVPIfEE0f0XQQ0u5pJtBsnk2/7OPiCFIPOe/w==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.npmjs.org/esbuild-linux-64/-/esbuild-linux-64-0.15.13.tgz"
-  integrity sha512-rXmnArVNio6yANSqDQlIO4WiP+Cv7+9EuAHNnag7rByAqFVuRusLbGi2697A5dFPNXoO//IiogVwi3AdcfPC6A==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-linux-arm64/-/esbuild-linux-arm64-0.15.13.tgz#9323c333924f97a02bdd2ae8912b36298acb312d"
-  integrity sha512-alEMGU4Z+d17U7KQQw2IV8tQycO6T+rOrgW8OS22Ua25x6kHxoG6Ngry6Aq6uranC+pNWNMB6aHFPh7aTQdORQ==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-linux-arm/-/esbuild-linux-arm-0.15.13.tgz#b407f47b3ae721fe4e00e19e9f19289bef87a111"
-  integrity sha512-Ac6LpfmJO8WhCMQmO253xX2IU2B3wPDbl4IvR0hnqcPrdfCaUa2j/lLMGTjmQ4W5JsJIdHEdW12dG8lFS0MbxQ==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-linux-mips64le/-/esbuild-linux-mips64le-0.15.13.tgz#bdf905aae5c0bcaa8f83567fe4c4c1bdc1f14447"
-  integrity sha512-47PgmyYEu+yN5rD/MbwS6DxP2FSGPo4Uxg5LwIdxTiyGC2XKwHhHyW7YYEDlSuXLQXEdTO7mYe8zQ74czP7W8A==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-linux-ppc64le/-/esbuild-linux-ppc64le-0.15.13.tgz#2911eae1c90ff58a3bd3259cb557235df25aa3b4"
-  integrity sha512-z6n28h2+PC1Ayle9DjKoBRcx/4cxHoOa2e689e2aDJSaKug3jXcQw7mM+GLg+9ydYoNzj8QxNL8ihOv/OnezhA==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-linux-riscv64/-/esbuild-linux-riscv64-0.15.13.tgz#1837c660be12b1d20d2a29c7189ea703f93e9265"
-  integrity sha512-+Lu4zuuXuQhgLUGyZloWCqTslcCAjMZH1k3Xc9MSEJEpEFdpsSU0sRDXAnk18FKOfEjhu4YMGaykx9xjtpA6ow==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-linux-s390x/-/esbuild-linux-s390x-0.15.13.tgz#d52880ece229d1bd10b2d936b792914ffb07c7fc"
-  integrity sha512-BMeXRljruf7J0TMxD5CIXS65y7puiZkAh+s4XFV9qy16SxOuMhxhVIXYLnbdfLrsYGFzx7U9mcdpFWkkvy/Uag==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-netbsd-64/-/esbuild-netbsd-64-0.15.13.tgz#de14da46f1d20352b43e15d97a80a8788275e6ed"
-  integrity sha512-EHj9QZOTel581JPj7UO3xYbltFTYnHy+SIqJVq6yd3KkCrsHRbapiPb0Lx3EOOtybBEE9EyqbmfW1NlSDsSzvQ==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-openbsd-64/-/esbuild-openbsd-64-0.15.13.tgz#45e8a5fd74d92ad8f732c43582369c7990f5a0ac"
-  integrity sha512-nkuDlIjF/sfUhfx8SKq0+U+Fgx5K9JcPq1mUodnxI0x4kBdCv46rOGWbuJ6eof2n3wdoCLccOoJAbg9ba/bT2w==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-sunos-64/-/esbuild-sunos-64-0.15.13.tgz#f646ac3da7aac521ee0fdbc192750c87da697806"
-  integrity sha512-jVeu2GfxZQ++6lRdY43CS0Tm/r4WuQQ0Pdsrxbw+aOrHQPHV0+LNOLnvbN28M7BSUGnJnHkHm2HozGgNGyeIRw==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-windows-32/-/esbuild-windows-32-0.15.13.tgz#fb4fe77c7591418880b3c9b5900adc4c094f2401"
-  integrity sha512-XoF2iBf0wnqo16SDq+aDGi/+QbaLFpkiRarPVssMh9KYbFNCqPLlGAWwDvxEVz+ywX6Si37J2AKm+AXq1kC0JA==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-windows-64/-/esbuild-windows-64-0.15.13.tgz#1fca8c654392c0c31bdaaed168becfea80e20660"
-  integrity sha512-Et6htEfGycjDrtqb2ng6nT+baesZPYQIW+HUEHK4D1ncggNrDNk3yoboYQ5KtiVrw/JaDMNttz8rrPubV/fvPQ==
-
-[email protected]:
-  version "0.15.13"
-  resolved "https://registry.yarnpkg.com/esbuild-windows-arm64/-/esbuild-windows-arm64-0.15.13.tgz#4ffd01b6b2888603f1584a2fe96b1f6a6f2b3dd8"
-  integrity sha512-3bv7tqntThQC9SWLRouMDmZnlOukBhOCTlkzNqzGCmrkCJI7io5LLjwJBOVY6kOUlIvdxbooNZwjtBvj+7uuVg==
-
-esbuild@^0.15.13:
-  version "0.15.13"
-  resolved "https://registry.npmjs.org/esbuild/-/esbuild-0.15.13.tgz"
-  integrity sha512-Cu3SC84oyzzhrK/YyN4iEVy2jZu5t2fz66HEOShHURcjSkOSAVL8C/gfUT+lDJxkVHpg8GZ10DD0rMHRPqMFaQ==
+esbuild@^0.16.0:
+  version "0.16.1"
+  resolved "https://registry.yarnpkg.com/esbuild/-/esbuild-0.16.1.tgz#c3b20a11f612f188a78efed63598b560caf1b365"
+  integrity sha512-XbnT9SXFcijZ9GYsay7z69rzSWKlW+Ze7+ULEecEkVAkDyzfA6DLbqGp//6F4hUh3FOydco8xQEejE6LxI1kyQ==
   optionalDependencies:
-    "@esbuild/android-arm" "0.15.13"
-    "@esbuild/linux-loong64" "0.15.13"
-    esbuild-android-64 "0.15.13"
-    esbuild-android-arm64 "0.15.13"
-    esbuild-darwin-64 "0.15.13"
-    esbuild-darwin-arm64 "0.15.13"
-    esbuild-freebsd-64 "0.15.13"
-    esbuild-freebsd-arm64 "0.15.13"
-    esbuild-linux-32 "0.15.13"
-    esbuild-linux-64 "0.15.13"
-    esbuild-linux-arm "0.15.13"
-    esbuild-linux-arm64 "0.15.13"
-    esbuild-linux-mips64le "0.15.13"
-    esbuild-linux-ppc64le "0.15.13"
-    esbuild-linux-riscv64 "0.15.13"
-    esbuild-linux-s390x "0.15.13"
-    esbuild-netbsd-64 "0.15.13"
-    esbuild-openbsd-64 "0.15.13"
-    esbuild-sunos-64 "0.15.13"
-    esbuild-windows-32 "0.15.13"
-    esbuild-windows-64 "0.15.13"
-    esbuild-windows-arm64 "0.15.13"
+    "@esbuild/android-arm" "0.16.1"
+    "@esbuild/android-arm64" "0.16.1"
+    "@esbuild/android-x64" "0.16.1"
+    "@esbuild/darwin-arm64" "0.16.1"
+    "@esbuild/darwin-x64" "0.16.1"
+    "@esbuild/freebsd-arm64" "0.16.1"
+    "@esbuild/freebsd-x64" "0.16.1"
+    "@esbuild/linux-arm" "0.16.1"
+    "@esbuild/linux-arm64" "0.16.1"
+    "@esbuild/linux-ia32" "0.16.1"
+    "@esbuild/linux-loong64" "0.16.1"
+    "@esbuild/linux-mips64el" "0.16.1"
+    "@esbuild/linux-ppc64" "0.16.1"
+    "@esbuild/linux-riscv64" "0.16.1"
+    "@esbuild/linux-s390x" "0.16.1"
+    "@esbuild/linux-x64" "0.16.1"
+    "@esbuild/netbsd-x64" "0.16.1"
+    "@esbuild/openbsd-x64" "0.16.1"
+    "@esbuild/sunos-x64" "0.16.1"
+    "@esbuild/win32-arm64" "0.16.1"
+    "@esbuild/win32-ia32" "0.16.1"
+    "@esbuild/win32-x64" "0.16.1"
 
 esprima@^4.0.0:
   version "4.0.1"