Bump esbuild from 0.19.5 to 0.19.8 (#7)

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.19.5 to 0.19.8.
<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.19.8</h2>
<ul>
<li>
<p>Add a treemap chart to esbuild's bundle analyzer (<a
href="https://redirect.github.com/evanw/esbuild/issues/2848">#2848</a>)</p>
<p>The bundler analyzer on esbuild's website (<a
href="https://esbuild.github.io/analyze/">https://esbuild.github.io/analyze/</a>)
now has a treemap chart type in addition to the two existing chart types
(sunburst and flame). This should be more familiar for people coming
from other similar tools, as well as make better use of large
screens.</p>
</li>
<li>
<p>Allow decorators after the <code>export</code> keyword (<a
href="https://redirect.github.com/evanw/esbuild/issues/104">#104</a>)</p>
<p>Previously esbuild's decorator parser followed the original behavior
of TypeScript's experimental decorators feature, which only allowed
decorators to come before the <code>export</code> keyword. However, the
upcoming JavaScript decorators feature also allows decorators to come
after the <code>export</code> keyword. And with TypeScript 5.0,
TypeScript now also allows experimental decorators to come after the
<code>export</code> keyword too. So esbuild now allows this as well:</p>
<pre lang="js"><code>// This old syntax has always been permitted:
@decorator export class Foo {}
@decorator export default class Foo {}
<p>// This new syntax is now permitted too:
export <a
href="https://github.com/decorator"><code>@​decorator</code></a> class
Foo {}
export default <a
href="https://github.com/decorator"><code>@​decorator</code></a> class
Foo {}
</code></pre></p>
<p>In addition, esbuild's decorator parser has been rewritten to fix
several subtle and likely unimportant edge cases with esbuild's parsing
of exports and decorators in TypeScript (e.g. TypeScript apparently does
automatic semicolon insertion after <code>interface</code> and
<code>export interface</code> but not after <code>export default
interface</code>).</p>
</li>
<li>
<p>Pretty-print decorators using the same whitespace as the original</p>
<p>When printing code containing decorators, esbuild will now try to
respect whether the original code contained newlines after the decorator
or not. This can make generated code containing many decorators much
more compact to read:</p>
<pre lang="js"><code>// Original code
class Foo {
  @A @b @c abc
  @x @y @z xyz
}
<p>// Old output
class Foo {
<a href="https://github.com/a"><code>@​a</code></a>
<a href="https://github.com/b"><code>@​b</code></a>
<a href="https://github.com/c"><code>@​c</code></a>
abc;
<a href="https://github.com/x"><code>@​x</code></a>
<a href="https://github.com/y"><code>@​y</code></a>
<a href="https://github.com/z"><code>@​z</code></a>
xyz;
}</p>
<p>// New output
class Foo {
<a href="https://github.com/a"><code>@​a</code></a> <a
href="https://github.com/b"><code>@​b</code></a> <a
href="https://github.com/c"><code>@​c</code></a> abc;
<a href="https://github.com/x"><code>@​x</code></a> <a
href="https://github.com/y"><code>@​y</code></a> <a
href="https://github.com/z"><code>@​z</code></a> xyz;
}
</code></pre></p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</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.19.8</h2>
<ul>
<li>
<p>Add a treemap chart to esbuild's bundle analyzer (<a
href="https://redirect.github.com/evanw/esbuild/issues/2848">#2848</a>)</p>
<p>The bundler analyzer on esbuild's website (<a
href="https://esbuild.github.io/analyze/">https://esbuild.github.io/analyze/</a>)
now has a treemap chart type in addition to the two existing chart types
(sunburst and flame). This should be more familiar for people coming
from other similar tools, as well as make better use of large
screens.</p>
</li>
<li>
<p>Allow decorators after the <code>export</code> keyword (<a
href="https://redirect.github.com/evanw/esbuild/issues/104">#104</a>)</p>
<p>Previously esbuild's decorator parser followed the original behavior
of TypeScript's experimental decorators feature, which only allowed
decorators to come before the <code>export</code> keyword. However, the
upcoming JavaScript decorators feature also allows decorators to come
after the <code>export</code> keyword. And with TypeScript 5.0,
TypeScript now also allows experimental decorators to come after the
<code>export</code> keyword too. So esbuild now allows this as well:</p>
<pre lang="js"><code>// This old syntax has always been permitted:
@decorator export class Foo {}
@decorator export default class Foo {}
<p>// This new syntax is now permitted too:
export <a
href="https://github.com/decorator"><code>@​decorator</code></a> class
Foo {}
export default <a
href="https://github.com/decorator"><code>@​decorator</code></a> class
Foo {}
</code></pre></p>
<p>In addition, esbuild's decorator parser has been rewritten to fix
several subtle and likely unimportant edge cases with esbuild's parsing
of exports and decorators in TypeScript (e.g. TypeScript apparently does
automatic semicolon insertion after <code>interface</code> and
<code>export interface</code> but not after <code>export default
interface</code>).</p>
</li>
<li>
<p>Pretty-print decorators using the same whitespace as the original</p>
<p>When printing code containing decorators, esbuild will now try to
respect whether the original code contained newlines after the decorator
or not. This can make generated code containing many decorators much
more compact to read:</p>
<pre lang="js"><code>// Original code
class Foo {
  @A @b @c abc
  @x @y @z xyz
}
<p>// Old output
class Foo {
<a href="https://github.com/a"><code>@​a</code></a>
<a href="https://github.com/b"><code>@​b</code></a>
<a href="https://github.com/c"><code>@​c</code></a>
abc;
<a href="https://github.com/x"><code>@​x</code></a>
<a href="https://github.com/y"><code>@​y</code></a>
<a href="https://github.com/z"><code>@​z</code></a>
xyz;
}</p>
<p>// New output
class Foo {
<a href="https://github.com/a"><code>@​a</code></a> <a
href="https://github.com/b"><code>@​b</code></a> <a
href="https://github.com/c"><code>@​c</code></a> abc;
<a href="https://github.com/x"><code>@​x</code></a> <a
href="https://github.com/y"><code>@​y</code></a> <a
href="https://github.com/z"><code>@​z</code></a> xyz;
}
</code></pre></p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/evanw/esbuild/commit/e97bd6706c7aaddb3770ae31b164d7ccaec8056c"><code>e97bd67</code></a>
publish 0.19.8 to npm</li>
<li><a
href="https://github.com/evanw/esbuild/commit/65b305894dc8bb3bae8a2a2c88f2b461135ef13f"><code>65b3058</code></a>
mention the treemap in the release notes (<a
href="https://redirect.github.com/evanw/esbuild/issues/2848">#2848</a>)</li>
<li><a
href="https://github.com/evanw/esbuild/commit/16883d42eb631aac354104a80cc41446b983bdf9"><code>16883d4</code></a>
add whitespace change to release notes</li>
<li><a
href="https://github.com/evanw/esbuild/commit/7383d0dbff033ae2f954a080a77b267eede303f9"><code>7383d0d</code></a>
decorators: printing preserves newline-tail status</li>
<li><a
href="https://github.com/evanw/esbuild/commit/7edc83da67e9bf5bb217401debf0669a7011e8b8"><code>7edc83d</code></a>
reword an experimental decorators error message</li>
<li><a
href="https://github.com/evanw/esbuild/commit/f3d535262e3998d845d0f102b944ecd5a9efda57"><code>f3d5352</code></a>
remove a now-unused field</li>
<li><a
href="https://github.com/evanw/esbuild/commit/e7551893c099e101f9491e2b79851671db4cd441"><code>e755189</code></a>
ts: forbid regular decorators on <code>declare</code> fields</li>
<li><a
href="https://github.com/evanw/esbuild/commit/69c9e7f9fa91db641ecbcfad40b9fd6977522f8a"><code>69c9e7f</code></a>
allow decorators to come after <code>export</code> (<a
href="https://redirect.github.com/evanw/esbuild/issues/104">#104</a>)</li>
<li><a
href="https://github.com/evanw/esbuild/commit/7baefdb4ea471d453a880a18fef5217347cf9973"><code>7baefdb</code></a>
fix a panic with &quot;export default interface\n&quot;</li>
<li><a
href="https://github.com/evanw/esbuild/commit/a8313d2c5d1e7574de92b3aade60c5c84fd31c59"><code>a8313d2</code></a>
use &quot;check&quot; for decorator validation, not
&quot;guess&quot;</li>
<li>Additional commits viewable in <a
href="https://github.com/evanw/esbuild/compare/v0.19.5...v0.19.8">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.19.5&new-version=0.19.8)](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>
Co-authored-by: anthony-nhs <[email protected]>