Upgrade: [dependabot] - bump esbuild from 0.21.2 to 0.21.3 (#260)

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.21.2 to 0.21.3.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/evanw/esbuild/releases">esbuild's
releases</a>.</em></p>
<blockquote>
<h2>v0.21.3</h2>
<ul>
<li>
<p>Implement the decorator metadata proposal (<a
href="https://redirect.github.com/evanw/esbuild/issues/3760">#3760</a>)</p>
<p>This release implements the <a
href="https://github.com/tc39/proposal-decorator-metadata">decorator
metadata proposal</a>, which is a sub-proposal of the <a
href="https://github.com/tc39/proposal-decorators">decorators
proposal</a>. Microsoft shipped the decorators proposal in <a
href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators">TypeScript
5.0</a> and the decorator metadata proposal in <a
href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#decorator-metadata">TypeScript
5.2</a>, so it's important that esbuild also supports both of these
features. Here's a quick example:</p>
<pre lang="js"><code>// Shim the &quot;Symbol.metadata&quot; symbol
Symbol.metadata ??= Symbol('Symbol.metadata')
<p>const track = (_, context) =&gt; {
(context.metadata.names ||= []).push(context.name)
}</p>
<p>class Foo {
<a href="https://github.com/track"><code>@​track</code></a> foo = 1
<a href="https://github.com/track"><code>@​track</code></a> bar = 2
}</p>
<p>// Prints [&quot;foo&quot;, &quot;bar&quot;]
console.log(Foo[Symbol.metadata].names)
</code></pre></p>
<p><strong>⚠️ WARNING ⚠️</strong></p>
<p>This proposal has been marked as &quot;stage 3&quot; which means
&quot;recommended for implementation&quot;. However, it's still a work
in progress and isn't a part of JavaScript yet, so keep in mind that any
code that uses JavaScript decorator metadata may need to be updated as
the feature continues to evolve. If/when that happens, I will update
esbuild's implementation to match the specification. I will not be
supporting old versions of the specification.</p>
</li>
<li>
<p>Fix bundled decorators in derived classes (<a
href="https://redirect.github.com/evanw/esbuild/issues/3768">#3768</a>)</p>
<p>In certain cases, bundling code that uses decorators in a derived
class with a class body that references its own class name could
previously generate code that crashes at run-time due to an incorrect
variable name. This problem has been fixed. Here is an example of code
that was compiled incorrectly before this fix:</p>
<pre lang="js"><code>class Foo extends Object {
  @(x =&gt; x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())
</code></pre>
</li>
<li>
<p>Fix <code>tsconfig.json</code> files inside symlinked directories (<a
href="https://redirect.github.com/evanw/esbuild/issues/3767">#3767</a>)</p>
<p>This release fixes an issue with a scenario involving a
<code>tsconfig.json</code> file that <code>extends</code> another file
from within a symlinked directory that uses the <code>paths</code>
feature. In that case, the implicit <code>baseURL</code> value should be
based on the real path (i.e. after expanding all symbolic links) instead
of the original path. This was already done for other files that esbuild
resolves but was not yet done for <code>tsconfig.json</code> because
it's special-cased (the regular path resolver can't be used because the
information inside <code>tsconfig.json</code> is involved in path
resolution). Note that this fix no longer applies if the
<code>--preserve-symlinks</code> setting is enabled.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/evanw/esbuild/blob/main/CHANGELOG.md">esbuild's
changelog</a>.</em></p>
<blockquote>
<h2>0.21.3</h2>
<ul>
<li>
<p>Implement the decorator metadata proposal (<a
href="https://redirect.github.com/evanw/esbuild/issues/3760">#3760</a>)</p>
<p>This release implements the <a
href="https://github.com/tc39/proposal-decorator-metadata">decorator
metadata proposal</a>, which is a sub-proposal of the <a
href="https://github.com/tc39/proposal-decorators">decorators
proposal</a>. Microsoft shipped the decorators proposal in <a
href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#decorators">TypeScript
5.0</a> and the decorator metadata proposal in <a
href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-2/#decorator-metadata">TypeScript
5.2</a>, so it's important that esbuild also supports both of these
features. Here's a quick example:</p>
<pre lang="js"><code>// Shim the &quot;Symbol.metadata&quot; symbol
Symbol.metadata ??= Symbol('Symbol.metadata')
<p>const track = (_, context) =&gt; {
(context.metadata.names ||= []).push(context.name)
}</p>
<p>class Foo {
<a href="https://github.com/track"><code>@​track</code></a> foo = 1
<a href="https://github.com/track"><code>@​track</code></a> bar = 2
}</p>
<p>// Prints [&quot;foo&quot;, &quot;bar&quot;]
console.log(Foo[Symbol.metadata].names)
</code></pre></p>
<p><strong>⚠️ WARNING ⚠️</strong></p>
<p>This proposal has been marked as &quot;stage 3&quot; which means
&quot;recommended for implementation&quot;. However, it's still a work
in progress and isn't a part of JavaScript yet, so keep in mind that any
code that uses JavaScript decorator metadata may need to be updated as
the feature continues to evolve. If/when that happens, I will update
esbuild's implementation to match the specification. I will not be
supporting old versions of the specification.</p>
</li>
<li>
<p>Fix bundled decorators in derived classes (<a
href="https://redirect.github.com/evanw/esbuild/issues/3768">#3768</a>)</p>
<p>In certain cases, bundling code that uses decorators in a derived
class with a class body that references its own class name could
previously generate code that crashes at run-time due to an incorrect
variable name. This problem has been fixed. Here is an example of code
that was compiled incorrectly before this fix:</p>
<pre lang="js"><code>class Foo extends Object {
  @(x =&gt; x) foo() {
    return Foo
  }
}
console.log(new Foo().foo())
</code></pre>
</li>
<li>
<p>Fix <code>tsconfig.json</code> files inside symlinked directories (<a
href="https://redirect.github.com/evanw/esbuild/issues/3767">#3767</a>)</p>
<p>This release fixes an issue with a scenario involving a
<code>tsconfig.json</code> file that <code>extends</code> another file
from within a symlinked directory that uses the <code>paths</code>
feature. In that case, the implicit <code>baseURL</code> value should be
based on the real path (i.e. after expanding all symbolic links) instead
of the original path. This was already done for other files that esbuild
resolves but was not yet done for <code>tsconfig.json</code> because
it's special-cased (the regular path resolver can't be used because the
information inside <code>tsconfig.json</code> is involved in path
resolution). Note that this fix no longer applies if the
<code>--preserve-symlinks</code> setting is enabled.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/evanw/esbuild/commit/efa3dd2d8e895f7f9a9bef0d588560bbae7d776e"><code>efa3dd2</code></a>
publish 0.21.3 to npm</li>
<li><a
href="https://github.com/evanw/esbuild/commit/5e7cf259752f500d75c5640b1d72fbf498be9dcd"><code>5e7cf25</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3760">#3760</a>:
implement decorator metadata proposal</li>
<li><a
href="https://github.com/evanw/esbuild/commit/bd0b13b969054752739beef7a63c1d076adf38a7"><code>bd0b13b</code></a>
lowering: always propagate class expression names</li>
<li><a
href="https://github.com/evanw/esbuild/commit/90acd14833b56f1f1335877f0b9d83837aadc6ea"><code>90acd14</code></a>
explicit bitwise operators for initializer flags</li>
<li><a
href="https://github.com/evanw/esbuild/commit/ba548dfd3224bf4029724e4db773008e93b6c74e"><code>ba548df</code></a>
move decorator initializer list to after the class</li>
<li><a
href="https://github.com/evanw/esbuild/commit/66b7c6d174e0fbe693c7d7545c7430ad20d47c39"><code>66b7c6d</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3768">#3768</a>:
bundled decorators in derived classes</li>
<li><a
href="https://github.com/evanw/esbuild/commit/6e6f15f9d6a32237ac68da2978de22ee25a2ae17"><code>6e6f15f</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3767">#3767</a>:
<code>tsconfig.json</code> files inside symlinks</li>
<li><a
href="https://github.com/evanw/esbuild/commit/b7dcb95dc5b03b530ec2618f471698f6e4f1d0f5"><code>b7dcb95</code></a>
transform: reuse <code>lowerField</code> for auto-accessors</li>
<li>See full diff in <a
href="https://github.com/evanw/esbuild/compare/v0.21.2...v0.21.3">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=esbuild&package-manager=npm_and_yarn&previous-version=0.21.2&new-version=0.21.3)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

package.json

@@ -46,6 +46,6 @@
   },
   "dependencies": {
     "conventional-changelog-eslint": "5.0.0",
-    "esbuild": "^0.21.2"
+    "esbuild": "^0.21.3"
   }
 }