Bump the ts-proto group in /impl/ts-proto with 5 updates (#260)

Bumps the ts-proto group in /impl/ts-proto with 5 updates:

| Package | From | To |
| --- | --- | --- |
| [ts-proto](https://github.com/stephenh/ts-proto) | `2.0.3` | `2.2.1` |
| [@bufbuild/buf](https://github.com/bufbuild/buf) | `1.39.0` | `1.43.0`
|
|
[@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node)
| `22.5.1` | `22.7.4` |
| [esbuild](https://github.com/evanw/esbuild) | `0.23.1` | `0.24.0` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.5.4` |
`5.6.2` |

Updates `ts-proto` from 2.0.3 to 2.2.1
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/stephenh/ts-proto/releases">ts-proto's
releases</a>.</em></p>
<blockquote>
<h2>v2.2.1</h2>
<h2><a
href="https://github.com/stephenh/ts-proto/compare/v2.2.0...v2.2.1">2.2.1</a>
(2024-09-29)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>Compilation error for nested repeated fields with
<code>useOptionals=all</code> (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1113">#1113</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/e89fc51fcc3ba494a81884cc136779202d3f1e16">e89fc51</a>),
closes <a
href="https://redirect.github.com/stephenh/ts-proto/issues/1112">#1112</a></li>
</ul>
<h2>v2.2.0</h2>
<h1><a
href="https://github.com/stephenh/ts-proto/compare/v2.1.0...v2.2.0">2.2.0</a>
(2024-09-06)</h1>
<h3>Features</h3>
<ul>
<li>Add interface for static message methods (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1104">#1104</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/faa33b6f5170cabe4010c95d5f0a68b9f04f686b">faa33b6</a>)</li>
</ul>
<h2>v2.1.0</h2>
<h1><a
href="https://github.com/stephenh/ts-proto/compare/v2.0.4...v2.1.0">2.1.0</a>
(2024-09-04)</h1>
<h3>Features</h3>
<ul>
<li>option to declare schema as const (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1096">#1096</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/4cc1a1e4238cf628591414c02d39bd76dc75fb3a">4cc1a1e</a>)</li>
</ul>
<h2>v2.0.4</h2>
<h2><a
href="https://github.com/stephenh/ts-proto/compare/v2.0.3...v2.0.4">2.0.4</a>
(2024-09-04)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>Bump ts-proto-descriptors. (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1102">#1102</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/3d1cd61ed7bbac4d6dc7353c49d0732aad22a504">3d1cd61</a>),
closes <a
href="https://redirect.github.com/stephenh/ts-proto/issues/1101">#1101</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/stephenh/ts-proto/blob/main/CHANGELOG.md">ts-proto's
changelog</a>.</em></p>
<blockquote>
<h2><a
href="https://github.com/stephenh/ts-proto/compare/v2.2.0...v2.2.1">2.2.1</a>
(2024-09-29)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>Compilation error for nested repeated fields with
<code>useOptionals=all</code> (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1113">#1113</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/e89fc51fcc3ba494a81884cc136779202d3f1e16">e89fc51</a>),
closes <a
href="https://redirect.github.com/stephenh/ts-proto/issues/1112">#1112</a></li>
</ul>
<h1><a
href="https://github.com/stephenh/ts-proto/compare/v2.1.0...v2.2.0">2.2.0</a>
(2024-09-06)</h1>
<h3>Features</h3>
<ul>
<li>Add interface for static message methods (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1104">#1104</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/faa33b6f5170cabe4010c95d5f0a68b9f04f686b">faa33b6</a>)</li>
</ul>
<h1><a
href="https://github.com/stephenh/ts-proto/compare/v2.0.4...v2.1.0">2.1.0</a>
(2024-09-04)</h1>
<h3>Features</h3>
<ul>
<li>option to declare schema as const (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1096">#1096</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/4cc1a1e4238cf628591414c02d39bd76dc75fb3a">4cc1a1e</a>)</li>
</ul>
<h2><a
href="https://github.com/stephenh/ts-proto/compare/v2.0.3...v2.0.4">2.0.4</a>
(2024-09-04)</h2>
<h3>Bug Fixes</h3>
<ul>
<li>Bump ts-proto-descriptors. (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1102">#1102</a>)
(<a
href="https://github.com/stephenh/ts-proto/commit/3d1cd61ed7bbac4d6dc7353c49d0732aad22a504">3d1cd61</a>),
closes <a
href="https://redirect.github.com/stephenh/ts-proto/issues/1101">#1101</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/stephenh/ts-proto/commit/6a8188e1cae80b14fcab17adc42cb06539d3fcd2"><code>6a8188e</code></a>
chore(release): 2.2.1 [skip ci]</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/e89fc51fcc3ba494a81884cc136779202d3f1e16"><code>e89fc51</code></a>
fix: Compilation error for nested repeated fields with
<code>useOptionals=all</code> (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1">#1</a>...</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/e8eaf9209f091e51c5219430985f587a58eda121"><code>e8eaf92</code></a>
chore: Pin dockerfile to node-22 for now.</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/ffacf3aaa8fad43c69e75a184c0703fc050b7868"><code>ffacf3a</code></a>
chore: Fix typos (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1108">#1108</a>)</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/58f2e584298dc61a0c74cd7c7226e2ba2f4d052a"><code>58f2e58</code></a>
chore(release): 2.2.0 [skip ci]</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/faa33b6f5170cabe4010c95d5f0a68b9f04f686b"><code>faa33b6</code></a>
feat: Add interface for static message methods (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1104">#1104</a>)</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/e42e8e719096b3b961adaabe379810f2a5d76324"><code>e42e8e7</code></a>
chore(release): 2.1.0 [skip ci]</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/4cc1a1e4238cf628591414c02d39bd76dc75fb3a"><code>4cc1a1e</code></a>
feat: option to declare schema as const (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1096">#1096</a>)</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/8ccb45982c53acd6ff5b3e4e7e88d1fc032de671"><code>8ccb459</code></a>
chore(release): 2.0.4 [skip ci]</li>
<li><a
href="https://github.com/stephenh/ts-proto/commit/3d1cd61ed7bbac4d6dc7353c49d0732aad22a504"><code>3d1cd61</code></a>
fix: Bump ts-proto-descriptors. (<a
href="https://redirect.github.com/stephenh/ts-proto/issues/1102">#1102</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/stephenh/ts-proto/compare/v2.0.3...v2.2.1">compare
view</a></li>
</ul>
</details>
<br />

Updates `@bufbuild/buf` from 1.39.0 to 1.43.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/bufbuild/buf/releases"><code>@​bufbuild/buf</code>'s
releases</a>.</em></p>
<blockquote>
<h2>v1.43.0</h2>
<ul>
<li>Add new experimental LSP support under <code>buf beta
lsp</code>.</li>
</ul>
<h2>v1.42.0</h2>
<ul>
<li>Add support for custom lint and breaking change plugins. See <a
href="https://buf.build/blog/buf-custom-lint-breaking-change-plugins">our
launch blog post</a> for more details!</li>
<li>Add <code>buf dep graph --format</code> flag that defaults to
<code>dot</code>, and adds the option <code>json</code>, to print the
dependency graph in JSON format.</li>
<li>Fix bugs in <code>buf format</code> where trailing comments on
commas in message literals were not properly propagated to the formatted
proto, empty message literals were not properly indented, and compound
strings in options added an extra newline before trailing commas.</li>
</ul>
<h2>v1.41.0</h2>
<ul>
<li>Add HTTP/3 support for gRPC with <code>buf curl</code>.</li>
<li>Fix issue where errors from protoc plugins may be overwritten when
executing plugins in parallel.</li>
</ul>
<h2>v1.40.1</h2>
<ul>
<li>Fix issue with <code>buf lint</code> where comment ignores in the
shape of <code>// buf:lint:ignore &lt;RULE_ID&gt; &lt;extra
comment&gt;</code> were not recognized due to the extra comment.</li>
</ul>
<h2>v1.40.0</h2>
<ul>
<li>Add concept of a default lint or breaking rule, which is printed out
as a property when running <code>buf config
ls-{breaking,lint}-rules</code>. Default rules are those rules which are
run if no lint or breaking rules are explicitly configured in your
<code>buf.yaml</code>.</li>
<li>Rename <code>DEFAULT</code> lint rule category to
<code>STANDARD</code>. With the concept of default rules being
introduced, having a category named <code>DEFAULT</code> is confusing,
as while it happens that all the rules in the <code>DEFAULT</code> lint
category are also default rules, the name has become overloaded. As with
all <code>buf</code> changes, this change is backwards-compatible: the
<code>DEFAULT</code> lint category continues to work, and always will.
We recommend changing to <code>STANDARD</code>, however.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/bufbuild/buf/blob/main/CHANGELOG.md"><code>@​bufbuild/buf</code>'s
changelog</a>.</em></p>
<blockquote>
<h2>[v1.43.0] - 2024-09-30</h2>
<ul>
<li>Add new experimental LSP support under <code>buf beta
lsp</code>.</li>
</ul>
<h2>[v1.42.0] - 2024-09-18</h2>
<ul>
<li>Add support for custom lint and breaking change plugins. See
<a
href="https://buf.build/blog/buf-custom-lint-breaking-change-plugins">our
launch blog post</a>
for more details!</li>
<li>Add <code>buf dep graph --format</code> flag that defaults to
<code>dot</code>, and adds the option <code>json</code>, to print
the dependency graph in JSON format.</li>
<li>Fix bugs in <code>buf format</code> where trailing comments on
commas in message literals were not properly
propagated to the formatted proto, empty message literals were not
properly indented, and
compound strings in options added an extra newline before trailing
commas.</li>
</ul>
<h2>[v1.41.0] - 2024-09-11</h2>
<ul>
<li>Add HTTP/3 support for gRPC with <code>buf curl</code>.</li>
<li>Fix issue where errors from protoc plugins may be overwritten when
executing plugins in parallel.</li>
</ul>
<h2>[v1.40.1] - 2024-09-06</h2>
<ul>
<li>Fix issue with <code>buf lint</code> where comment ignores in the
shape of <code>// buf:lint:ignore &lt;RULE_ID&gt; &lt;extra
comment&gt;</code>
were not recognized due to the extra comment.</li>
</ul>
<h2>[v1.40.0] - 2024-09-04</h2>
<ul>
<li>Add concept of a default lint or breaking rule, which is printed out
as a property when running
<code>buf config ls-{breaking,lint}-rules</code>. Default rules are
those rules which are run if no lint
or breaking rules are explicitly configured in your
<code>buf.yaml</code>.</li>
<li>Rename <code>DEFAULT</code> lint rule category to
<code>STANDARD</code>. With the concept of default rules being
introduced,
having a category named <code>DEFAULT</code> is confusing, as while it
happens that all the rules in the <code>DEFAULT</code>
lint category are also default rules, the name has become overloaded. As
with all <code>buf</code> changes, this
change is backwards-compatible: the <code>DEFAULT</code> lint category
continues to work, and always will. We
recommend changing to <code>STANDARD</code>, however.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/bufbuild/buf/commit/e31cbd0f4e3a0249eba29c977b5bf99ce5bf2c2a"><code>e31cbd0</code></a>
Release v1.43.0 (<a
href="https://redirect.github.com/bufbuild/buf/issues/3357">#3357</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/6abbe9d67317d10146eceba747c92bac3d65f83c"><code>6abbe9d</code></a>
Make upgrade (<a
href="https://redirect.github.com/bufbuild/buf/issues/3354">#3354</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/4ef2306be29ee97dedb88aac70b6827bcec671ec"><code>4ef2306</code></a>
Make upgrade (<a
href="https://redirect.github.com/bufbuild/buf/issues/3352">#3352</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/e3017a551e6e549b3d4cf3f8bab9c82b94edbf09"><code>e3017a5</code></a>
Move to buf.build/go/spdx (<a
href="https://redirect.github.com/bufbuild/buf/issues/3350">#3350</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/fd749ca09211704eef9e7c8b7bc72c39d0d2ef8c"><code>fd749ca</code></a>
Unbreak CI after <a
href="https://redirect.github.com/bufbuild/buf/issues/3316">#3316</a>
(<a
href="https://redirect.github.com/bufbuild/buf/issues/3348">#3348</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/b8aeca11e1385797c7273d4ad2e10bb3869352f3"><code>b8aeca1</code></a>
Force usage of private/pkg/protoencoding for text and yaml (<a
href="https://redirect.github.com/bufbuild/buf/issues/3347">#3347</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/c8517325696e2d0ecd9aa4e41c6feee399e30dde"><code>c851732</code></a>
Default protoencoding resolver to an empty resolver (<a
href="https://redirect.github.com/bufbuild/buf/issues/3345">#3345</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/8c2163946b5def59c9340b204a254939fbac7e62"><code>8c21639</code></a>
Add an LSP server command (<a
href="https://redirect.github.com/bufbuild/buf/issues/3316">#3316</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/a4fb701e7e6b3236f2daaca6ae553b1239c2cffb"><code>a4fb701</code></a>
Force usage of private/pkg/protoencoding (<a
href="https://redirect.github.com/bufbuild/buf/issues/3346">#3346</a>)</li>
<li><a
href="https://github.com/bufbuild/buf/commit/dacb299b7e85cd9e4bccfc4cb8dd6443d4472290"><code>dacb299</code></a>
Reparse all extensions, not just unrecognized ones (<a
href="https://redirect.github.com/bufbuild/buf/issues/3344">#3344</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/bufbuild/buf/compare/v1.39.0...v1.43.0">compare
view</a></li>
</ul>
</details>
<br />

Updates `@types/node` from 22.5.1 to 22.7.4
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a
href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">compare
view</a></li>
</ul>
</details>
<br />

Updates `esbuild` from 0.23.1 to 0.24.0
<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.24.0</h2>
<p><strong><em>This release deliberately contains backwards-incompatible
changes.</em></strong> To avoid automatically picking up releases like
this, you should either be pinning the exact version of
<code>esbuild</code> in your <code>package.json</code> file
(recommended) or be using a version range syntax that only accepts patch
upgrades such as <code>^0.23.0</code> or <code>~0.23.0</code>. See npm's
documentation about <a
href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for
more information.</p>
<ul>
<li>
<p>Drop support for older platforms (<a
href="https://redirect.github.com/evanw/esbuild/pull/3902">#3902</a>)</p>
<p>This release drops support for the following operating system:</p>
<ul>
<li>macOS 10.15 Catalina</li>
</ul>
<p>This is because the Go programming language dropped support for this
operating system version in Go 1.23, and this release updates esbuild
from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or
later.</p>
<p>Note that this only affects the binary esbuild executables that are
published to the esbuild npm package. It's still possible to compile
esbuild's source code for these older operating systems. If you need to,
you can compile esbuild for yourself using an older version of the Go
compiler (before Go version 1.23). That might look something like
this:</p>
<pre><code>git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
</code></pre>
</li>
<li>
<p>Fix class field decorators in TypeScript if
<code>useDefineForClassFields</code> is <code>false</code> (<a
href="https://redirect.github.com/evanw/esbuild/issues/3913">#3913</a>)</p>
<p>Setting the <code>useDefineForClassFields</code> flag to
<code>false</code> in <code>tsconfig.json</code> means class fields use
the legacy TypeScript behavior instead of the standard JavaScript
behavior. Specifically they use assign semantics instead of define
semantics (e.g. setters are triggered) and fields without an initializer
are not initialized at all. However, when this legacy behavior is
combined with standard JavaScript decorators, TypeScript switches to
always initializing all fields, even those without initializers.
Previously esbuild incorrectly continued to omit field initializers for
this edge case. These field initializers in this case should now be
emitted starting with this release.</p>
</li>
<li>
<p>Avoid incorrect cycle warning with <code>tsconfig.json</code>
multiple inheritance (<a
href="https://redirect.github.com/evanw/esbuild/issues/3898">#3898</a>)</p>
<p>TypeScript 5.0 introduced multiple inheritance for
<code>tsconfig.json</code> files where <code>extends</code> can be an
array of file paths. Previously esbuild would incorrectly treat files
encountered more than once when processing separate subtrees of the
multiple inheritance hierarchy as an inheritance cycle. With this
release, <code>tsconfig.json</code> files containing this edge case
should work correctly without generating a warning.</p>
</li>
<li>
<p>Handle Yarn Plug'n'Play stack overflow with
<code>tsconfig.json</code> (<a
href="https://redirect.github.com/evanw/esbuild/issues/3915">#3915</a>)</p>
<p>Previously a <code>tsconfig.json</code> file that
<code>extends</code> another file in a package with an
<code>exports</code> map could cause a stack overflow when Yarn's
Plug'n'Play resolution was active. This edge case should work now
starting with this release.</p>
</li>
<li>
<p>Work around more issues with Deno 1.31+ (<a
href="https://redirect.github.com/evanw/esbuild/pull/3917">#3917</a>)</p>
<p>This version of Deno broke the <code>stdin</code> and
<code>stdout</code> properties on command objects for inherited streams,
which matters when you run esbuild's Deno module as the entry point
(i.e. when <code>import.meta.main</code> is <code>true</code>).
Previously esbuild would crash in Deno 1.31+ if you ran esbuild like
that. This should be fixed starting with this release.</p>
<p>This fix was contributed by <a
href="https://github.com/Joshix-1"><code>@​Joshix-1</code></a>.</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.24.0</h2>
<p><strong><em>This release deliberately contains backwards-incompatible
changes.</em></strong> To avoid automatically picking up releases like
this, you should either be pinning the exact version of
<code>esbuild</code> in your <code>package.json</code> file
(recommended) or be using a version range syntax that only accepts patch
upgrades such as <code>^0.23.0</code> or <code>~0.23.0</code>. See npm's
documentation about <a
href="https://docs.npmjs.com/cli/v6/using-npm/semver/">semver</a> for
more information.</p>
<ul>
<li>
<p>Drop support for older platforms (<a
href="https://redirect.github.com/evanw/esbuild/pull/3902">#3902</a>)</p>
<p>This release drops support for the following operating system:</p>
<ul>
<li>macOS 10.15 Catalina</li>
</ul>
<p>This is because the Go programming language dropped support for this
operating system version in Go 1.23, and this release updates esbuild
from Go 1.22 to Go 1.23. Go 1.23 now requires macOS 11 Big Sur or
later.</p>
<p>Note that this only affects the binary esbuild executables that are
published to the esbuild npm package. It's still possible to compile
esbuild's source code for these older operating systems. If you need to,
you can compile esbuild for yourself using an older version of the Go
compiler (before Go version 1.23). That might look something like
this:</p>
<pre><code>git clone https://github.com/evanw/esbuild.git
cd esbuild
go build ./cmd/esbuild
./esbuild --version
</code></pre>
</li>
<li>
<p>Fix class field decorators in TypeScript if
<code>useDefineForClassFields</code> is <code>false</code> (<a
href="https://redirect.github.com/evanw/esbuild/issues/3913">#3913</a>)</p>
<p>Setting the <code>useDefineForClassFields</code> flag to
<code>false</code> in <code>tsconfig.json</code> means class fields use
the legacy TypeScript behavior instead of the standard JavaScript
behavior. Specifically they use assign semantics instead of define
semantics (e.g. setters are triggered) and fields without an initializer
are not initialized at all. However, when this legacy behavior is
combined with standard JavaScript decorators, TypeScript switches to
always initializing all fields, even those without initializers.
Previously esbuild incorrectly continued to omit field initializers for
this edge case. These field initializers in this case should now be
emitted starting with this release.</p>
</li>
<li>
<p>Avoid incorrect cycle warning with <code>tsconfig.json</code>
multiple inheritance (<a
href="https://redirect.github.com/evanw/esbuild/issues/3898">#3898</a>)</p>
<p>TypeScript 5.0 introduced multiple inheritance for
<code>tsconfig.json</code> files where <code>extends</code> can be an
array of file paths. Previously esbuild would incorrectly treat files
encountered more than once when processing separate subtrees of the
multiple inheritance hierarchy as an inheritance cycle. With this
release, <code>tsconfig.json</code> files containing this edge case
should work correctly without generating a warning.</p>
</li>
<li>
<p>Handle Yarn Plug'n'Play stack overflow with
<code>tsconfig.json</code> (<a
href="https://redirect.github.com/evanw/esbuild/issues/3915">#3915</a>)</p>
<p>Previously a <code>tsconfig.json</code> file that
<code>extends</code> another file in a package with an
<code>exports</code> map could cause a stack overflow when Yarn's
Plug'n'Play resolution was active. This edge case should work now
starting with this release.</p>
</li>
<li>
<p>Work around more issues with Deno 1.31+ (<a
href="https://redirect.github.com/evanw/esbuild/pull/3917">#3917</a>)</p>
<p>This version of Deno broke the <code>stdin</code> and
<code>stdout</code> properties on command objects for inherited streams,
which matters when you run esbuild's Deno module as the entry point
(i.e. when <code>import.meta.main</code> is <code>true</code>).
Previously esbuild would crash in Deno 1.31+ if you ran esbuild like
that. This should be fixed starting with this release.</p>
<p>This fix was contributed by <a
href="https://github.com/Joshix-1"><code>@​Joshix-1</code></a>.</p>
</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/evanw/esbuild/commit/d34e79e2a998c21bb71d57b92b0017ca11756912"><code>d34e79e</code></a>
publish 0.24.0 to npm</li>
<li><a
href="https://github.com/evanw/esbuild/commit/045a87f164b31838aad7e2bcba112cf7717898d0"><code>045a87f</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3887">#3887</a>:
omit dead export warning for <code>default</code></li>
<li><a
href="https://github.com/evanw/esbuild/commit/6e049b81d2e080ccdf24db84a71934ea736879ce"><code>6e049b8</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3913">#3913</a>:
useDefineForClassFields and decorators</li>
<li><a
href="https://github.com/evanw/esbuild/commit/9c26f987dd9bbd33861a86b2a9d0b347f9ec297e"><code>9c26f98</code></a>
lower decorators for useDefineForClassFields <a
href="https://redirect.github.com/evanw/esbuild/issues/3913">#3913</a></li>
<li><a
href="https://github.com/evanw/esbuild/commit/46fdb686e2880f5b8447f998dedfc730e66ae32a"><code>46fdb68</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3898">#3898</a>:
incorrect cyclic tsconfig.json warning</li>
<li><a
href="https://github.com/evanw/esbuild/commit/b50044303b3430ce007ac0fe4baf21160093794e"><code>b500443</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3917">#3917</a>:
running esbuild cli with deno</li>
<li><a
href="https://github.com/evanw/esbuild/commit/b125e62c7033e3ace20df9ec05c846d222f61ce5"><code>b125e62</code></a>
run <code>make update-compat-table</code></li>
<li><a
href="https://github.com/evanw/esbuild/commit/112b9aa32ea80eeef01cb91a8b415cfff08ef850"><code>112b9aa</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3915">#3915</a>:
stack overflow with yarn + tsconfig</li>
<li><a
href="https://github.com/evanw/esbuild/commit/ed5a555488a18e3b48954506e98d1f6a51f53368"><code>ed5a555</code></a>
wasm: catch and rethrow stack overflows (<a
href="https://redirect.github.com/evanw/esbuild/issues/3915">#3915</a>)</li>
<li><a
href="https://github.com/evanw/esbuild/commit/11d3196156b12b11a3dc68f9d00a4a9982b907c0"><code>11d3196</code></a>
fix <a
href="https://redirect.github.com/evanw/esbuild/issues/3902">#3902</a>:
update go 1.22.5 =&gt; 1.23.1</li>
<li>Additional commits viewable in <a
href="https://github.com/evanw/esbuild/compare/v0.23.1...v0.24.0">compare
view</a></li>
</ul>
</details>
<br />

Updates `typescript` from 5.5.4 to 5.6.2
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/microsoft/TypeScript/releases">typescript's
releases</a>.</em></p>
<blockquote>
<h2>TypeScript 5.6</h2>
<p>For release notes, check out the <a
href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-6/">release
announcement</a>.</p>
<p>For the complete list of fixed issues, check out the</p>
<ul>
<li><a
href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&amp;q=milestone%3A%22TypeScript+5.6.0%22+is%3Aclosed+">fixed
issues query for Typescript 5.6.0 (Beta)</a>.</li>
<li><a
href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&amp;q=milestone%3A%22TypeScript+5.6.1%22+is%3Aclosed+">fixed
issues query for Typescript 5.6.1 (RC)</a>.</li>
<li><a
href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&amp;q=milestone%3A%22TypeScript+5.6.2%22+is%3Aclosed+">fixed
issues query for Typescript 5.6.2 (Stable)</a>.</li>
</ul>
<p>Downloads are available on:</p>
<ul>
<li><a href="https://www.npmjs.com/package/typescript">npm</a></li>
<li><a
href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet
package</a></li>
</ul>
<h2>TypeScript 5.6 RC</h2>
<p>For release notes, check out the <a
href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-6-rc/">release
announcement</a>.</p>
<p>For the complete list of fixed issues, check out the</p>
<ul>
<li><a
href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&amp;milestone%3A%22TypeScript+5.6.1%22+is%3Aclosed+">fixed
issues query for TypeScript v5.6.1 (RC)</a>.</li>
<li><a
href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&amp;milestone%3A%22TypeScript+5.6.0%22+is%3Aclosed+">fixed
issues query for TypeScript v5.6.0 (Beta)</a>.</li>
</ul>
<p>Downloads are available on:</p>
<ul>
<li><a href="https://www.npmjs.com/package/typescript">npm</a></li>
</ul>
<h2>TypeScript 5.6 Beta</h2>
<p>For release notes, check out the <a
href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-6-beta/">release
announcement</a>.</p>
<p>For the complete list of fixed issues, check out the</p>
<ul>
<li><a
href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&amp;q=milestone%3A%22TypeScript+5.6.0%22+is%3Aclosed+">fixed
issues query for Typescript 5.6.0 (Beta)</a>.</li>
</ul>
<p>Downloads are available on:</p>
<ul>
<li><a href="https://www.npmjs.com/package/typescript">npm</a></li>
<li><a
href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet
package</a></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/microsoft/TypeScript/commit/a7e3374f13327483fbe94e32806d65785b0b6cda"><code>a7e3374</code></a>
Bump version to 5.6.2 and LKG</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/20633579fcf88f6b61774349740de4841d2b8b5c"><code>2063357</code></a>
🤖 Pick PR <a
href="https://redirect.github.com/microsoft/TypeScript/issues/59708">#59708</a>
(LEGO: Pull request from lego/hb_537...) into release-5.6 (#...</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/4fe7e41ea1a92ecbd59119666be2d60164785391"><code>4fe7e41</code></a>
🤖 Pick PR <a
href="https://redirect.github.com/microsoft/TypeScript/issues/59670">#59670</a>
(fix(59649): ts Move to a new file d...) into release-5.6 (#...</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/1a03e5340ae0b83ce1b1f743763625f89e92ca91"><code>1a03e53</code></a>
🤖 Pick PR <a
href="https://redirect.github.com/microsoft/TypeScript/issues/59761">#59761</a>
(<code>this</code> can be nullish) into release-5.6 (<a
href="https://redirect.github.com/microsoft/TypeScript/issues/59762">#59762</a>)</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/6212132b835145b1a8fd49982680ac668caf3ddc"><code>6212132</code></a>
Update LKG</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/bbb5faf7e749df52adafdcd37c09ac7fff30ddaf"><code>bbb5faf</code></a>
🤖 Pick PR <a
href="https://redirect.github.com/microsoft/TypeScript/issues/59542">#59542</a>
(Fixing delay caused in vscode due t...) into release-5.6 (#...</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/e6914a558775bd3ba3dc5567877604a0864b9338"><code>e6914a5</code></a>
Bump version to 5.6.1-rc and LKG</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/34121c42b638e973f28b438b0513796a37585448"><code>34121c4</code></a>
Update LKG</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/2a30c2a8f0408b32c8c7ff88f0bf1c6a32e67704"><code>2a30c2a</code></a>
Merge remote-tracking branch 'origin/main' into release-5.6</li>
<li><a
href="https://github.com/microsoft/TypeScript/commit/936a79bbb58f82b173f6b644974995851b9b479e"><code>936a79b</code></a>
Expose TypeChecker. getAwaitedType to public (<a
href="https://redirect.github.com/microsoft/TypeScript/issues/59268">#59268</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/microsoft/TypeScript/compare/v5.5.4...v5.6.2">compare
view</a></li>
</ul>
</details>
<br />


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 <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions


</details>

---------

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