MINOR: [JS] Bump esbuild from 0.18.0 to 0.19.0 in /js (#37081)

Bumps [esbuild](https://github.com/evanw/esbuild) from 0.18.0 to 0.19.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.19.0</h2>
<p><strong>This release deliberately contains backwards-incompatible changes.</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.18.0</code> or <code>~0.18.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>Handle import paths containing wildcards (<a href="https://redirect.github.com/evanw/esbuild/issues/56">#56</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/700">#700</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/875">#875</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/976">#976</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/2221">#2221</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/2515">#2515</a>)</p>
<p>This release introduces wildcards in import paths in two places:</p>
<ul>
<li>
<p><strong>Entry points</strong></p>
<p>You can now pass a string containing glob-style wildcards such as <code>./src/*.ts</code> as an entry point and esbuild will search the file system for files that match the pattern. This can be used to easily pass esbuild all files with a certain extension on the command line in a cross-platform way. Previously you had to rely on the shell to perform glob expansion, but that is obviously shell-dependent and didn't work at all on Windows. Note that to use this feature on the command line you will have to quote the pattern so it's passed verbatim to esbuild without any expansion by the shell. Here's an example:</p>
<pre lang="sh"><code>esbuild --minify &quot;./src/*.ts&quot; --outdir=out
</code></pre>
<p>Specifically the <code>*</code> character will match any character except for the <code>/</code> character, and the <code>/**/</code> character sequence will match a path separator followed by zero or more path elements. Other wildcard operators found in glob patterns such as <code>?</code> and <code>[...]</code> are not supported.</p>
</li>
<li>
<p><strong>Run-time import paths</strong></p>
<p>Import paths that are evaluated at run-time can now be bundled in certain limited situations. The import path expression must be a form of string concatenation and must start with either <code>./</code> or <code>../</code>. Each non-string expression in the string concatenation chain becomes a wildcard. The <code>*</code> wildcard is chosen unless the previous character is a <code>/</code>, in which case the <code>/**/*</code> character sequence is used. Some examples:</p>
<pre lang="js"><code>// These two forms are equivalent
const json1 = await import('./data/' + kind + '.json')
const json2 = await import(`./data/${kind}.json`)
</code></pre>
<p>This feature works with <code>require(...)</code> and <code>import(...)</code> because these can all accept run-time expressions. It does not work with <code>import</code> and <code>export</code> statements because these cannot accept run-time expressions. If you want to prevent esbuild from trying to bundle these imports, you should move the string concatenation expression outside of the <code>require(...)</code> or <code>import(...)</code>. For example:</p>
<pre lang="js"><code>// This will be bundled
const json1 = await import('./data/' + kind + '.json')
<p>// This will not be bundled
const path = './data/' + kind + '.json'
const json2 = await import(path)
</code></pre></p>
<p>Note that using this feature means esbuild will potentially do a lot of file system I/O to find all possible files that might match the pattern. This is by design, and is not a bug. If this is a concern, I recommend either avoiding the <code>/**/</code> pattern (e.g. by not putting a <code>/</code> before a wildcard) or using this feature only in directory subtrees which do not have many files that don't match the pattern (e.g. making a subdirectory for your JSON files and explicitly including that subdirectory in the pattern).</p>
</li>
</ul>
</li>
<li>
<p>Path aliases in <code>tsconfig.json</code> no longer count as packages (<a href="https://redirect.github.com/evanw/esbuild/issues/2792">#2792</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3003">#3003</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3160">#3160</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3238">#3238</a>)</p>
<p>Setting <code>--packages=external</code> tells esbuild to make all import paths external when they look like a package path. For example, an import of <code>./foo/bar</code> is not a package path and won't be external while an import of <code>foo/bar</code> is a package path and will be external. However, the <a href="https://www.typescriptlang.org/tsconfig#paths"><code>paths</code> field</a> in <code>tsconfig.json</code> allows you to create import paths that look like package paths but that do not resolve to packages. People do not want these paths to count as package paths. So with this release, the behavior of <code>--packages=external</code> has been changed to happen after the <code>tsconfig.json</code> path remapping step.</p>
</li>
<li>
<p>Use the <code>local-css</code> loader for <code>.module.css</code> files by default (<a href="https://redirect.github.com/evanw/esbuild/issues/20">#20</a>)</p>
<p>With this release the <code>css</code> loader is still used for <code>.css</code> files except that <code>.module.css</code> files now use the <code>local-css</code> loader. This is a common convention in the web development community. If you need <code>.module.css</code> files to use the <code>css</code> loader instead, then you can override this behavior with <code>--loader:.module.css=css</code>.</p>
</li>
</ul>
<h2>v0.18.20</h2>
<ul>
<li>Support advanced CSS <code>@ import</code> rules (<a href="https://redirect.github.com/evanw/esbuild/issues/953">#953</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3137">#3137</a>)</li>
</ul>

</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.0</h2>
<p><strong>This release deliberately contains backwards-incompatible changes.</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.18.0</code> or <code>~0.18.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>Handle import paths containing wildcards (<a href="https://redirect.github.com/evanw/esbuild/issues/56">#56</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/700">#700</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/875">#875</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/976">#976</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/2221">#2221</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/2515">#2515</a>)</p>
<p>This release introduces wildcards in import paths in two places:</p>
<ul>
<li>
<p><strong>Entry points</strong></p>
<p>You can now pass a string containing glob-style wildcards such as <code>./src/*.ts</code> as an entry point and esbuild will search the file system for files that match the pattern. This can be used to easily pass esbuild all files with a certain extension on the command line in a cross-platform way. Previously you had to rely on the shell to perform glob expansion, but that is obviously shell-dependent and didn't work at all on Windows. Note that to use this feature on the command line you will have to quote the pattern so it's passed verbatim to esbuild without any expansion by the shell. Here's an example:</p>
<pre lang="sh"><code>esbuild --minify &quot;./src/*.ts&quot; --outdir=out
</code></pre>
<p>Specifically the <code>*</code> character will match any character except for the <code>/</code> character, and the <code>/**/</code> character sequence will match a path separator followed by zero or more path elements. Other wildcard operators found in glob patterns such as <code>?</code> and <code>[...]</code> are not supported.</p>
</li>
<li>
<p><strong>Run-time import paths</strong></p>
<p>Import paths that are evaluated at run-time can now be bundled in certain limited situations. The import path expression must be a form of string concatenation and must start with either <code>./</code> or <code>../</code>. Each non-string expression in the string concatenation chain becomes a wildcard. The <code>*</code> wildcard is chosen unless the previous character is a <code>/</code>, in which case the <code>/**/*</code> character sequence is used. Some examples:</p>
<pre lang="js"><code>// These two forms are equivalent
const json1 = await import('./data/' + kind + '.json')
const json2 = await import(`./data/${kind}.json`)
</code></pre>
<p>This feature works with <code>require(...)</code> and <code>import(...)</code> because these can all accept run-time expressions. It does not work with <code>import</code> and <code>export</code> statements because these cannot accept run-time expressions. If you want to prevent esbuild from trying to bundle these imports, you should move the string concatenation expression outside of the <code>require(...)</code> or <code>import(...)</code>. For example:</p>
<pre lang="js"><code>// This will be bundled
const json1 = await import('./data/' + kind + '.json')
<p>// This will not be bundled
const path = './data/' + kind + '.json'
const json2 = await import(path)
</code></pre></p>
<p>Note that using this feature means esbuild will potentially do a lot of file system I/O to find all possible files that might match the pattern. This is by design, and is not a bug. If this is a concern, I recommend either avoiding the <code>/**/</code> pattern (e.g. by not putting a <code>/</code> before a wildcard) or using this feature only in directory subtrees which do not have many files that don't match the pattern (e.g. making a subdirectory for your JSON files and explicitly including that subdirectory in the pattern).</p>
</li>
</ul>
</li>
<li>
<p>Path aliases in <code>tsconfig.json</code> no longer count as packages (<a href="https://redirect.github.com/evanw/esbuild/issues/2792">#2792</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3003">#3003</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3160">#3160</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3238">#3238</a>)</p>
<p>Setting <code>--packages=external</code> tells esbuild to make all import paths external when they look like a package path. For example, an import of <code>./foo/bar</code> is not a package path and won't be external while an import of <code>foo/bar</code> is a package path and will be external. However, the <a href="https://www.typescriptlang.org/tsconfig#paths"><code>paths</code> field</a> in <code>tsconfig.json</code> allows you to create import paths that look like package paths but that do not resolve to packages. People do not want these paths to count as package paths. So with this release, the behavior of <code>--packages=external</code> has been changed to happen after the <code>tsconfig.json</code> path remapping step.</p>
</li>
<li>
<p>Use the <code>local-css</code> loader for <code>.module.css</code> files by default (<a href="https://redirect.github.com/evanw/esbuild/issues/20">#20</a>)</p>
<p>With this release the <code>css</code> loader is still used for <code>.css</code> files except that <code>.module.css</code> files now use the <code>local-css</code> loader. This is a common convention in the web development community. If you need <code>.module.css</code> files to use the <code>css</code> loader instead, then you can override this behavior with <code>--loader:.module.css=css</code>.</p>
</li>
</ul>
<h2>0.18.20</h2>

</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/evanw/esbuild/commit/c337498cdad8cac87517ec49c923441b2dc67bf2"><code>c337498</code></a> publish 0.19.0 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/0b79ab2bc1716a4206a61a7bb0bb25357e1ac55d"><code>0b79ab2</code></a> this is a breaking change release</li>
<li><a href="https://github.com/evanw/esbuild/commit/cb464592283c63cb25b1707047dcc0f19da64283"><code>cb46459</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3003">#3003</a>, fix <a href="https://redirect.github.com/evanw/esbuild/issues/3238">#3238</a>: <code>--packages=</code> and <code>tsconfig</code></li>
<li><a href="https://github.com/evanw/esbuild/commit/727e5ff8bcf0459bcc341c64c9af8f6e0563fa4b"><code>727e5ff</code></a> css: use <code>local-css</code> for <code>.module.css</code> files (<a href="https://redirect.github.com/evanw/esbuild/issues/20">#20</a>)</li>
<li><a href="https://github.com/evanw/esbuild/commit/be9f8e5cd6703da9d9b9e4bea07cfc6e42b5856d"><code>be9f8e5</code></a> implement glob-style path resolution</li>
<li><a href="https://github.com/evanw/esbuild/commit/8e14e25f26d00149720484ba340072a714aed772"><code>8e14e25</code></a> add the <code>__glob</code> runtime helper method</li>
<li><a href="https://github.com/evanw/esbuild/commit/c067c5eae69fa42e72a551d6f2ea41ef07b37ed9"><code>c067c5e</code></a> remove an unnecessary argument</li>
<li><a href="https://github.com/evanw/esbuild/commit/6e05434eeeb9b4b257bafd6d96e0bac08af57f76"><code>6e05434</code></a> Update README.md</li>
<li><a href="https://github.com/evanw/esbuild/commit/22f0818cf81024b63752d815c51fe737612b43ec"><code>22f0818</code></a> publish 0.18.20 to npm</li>
<li><a href="https://github.com/evanw/esbuild/commit/89b98d923cf8c08ac30eb3e6b3e59eb5a4cab632"><code>89b98d9</code></a> css: test coverage for some external test cases</li>
<li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.18.0...v0.19.0">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.18.0&new-version=0.19.0)](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>

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

js/package.json

@@ -79,7 +79,7 @@
     "cross-env": "7.0.3",
     "del": "7.0.0",
     "del-cli": "5.0.0",
-    "esbuild": "0.18.0",
+    "esbuild": "0.19.0",
     "esbuild-plugin-alias": "0.2.1",
     "eslint": "8.42.0",
     "eslint-plugin-jest": "27.2.3",