dependabot[bot] opened a new pull request, #31219: URL: https://github.com/apache/superset/pull/31219
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.20.0 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> <h2>v0.23.1</h2> <ul> <li> <p>Allow using the <code>node:</code> import prefix with <code>es*</code> targets (<a href="https://redirect.github.com/evanw/esbuild/issues/3821";>#3821</a>)</p> <p>The <a href="https://nodejs.org/api/esm.html#node-imports";><code>node:</code> prefix on imports</a> is an alternate way to import built-in node modules. For example, <code>import fs from "fs"</code> can also be written <code>import fs from "node:fs"</code>. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with <code>--target=node14</code> so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as <code>--target=node18,es2022</code> removes the <code>node:</code> prefix because none of the <code>es*</code> targets are known to support this feature. This release adds the support for the <code>node:</code> flag to esbuild's internal compatibility table for <code>es*</code> to allow you to use compound targets like this:</p > <pre lang="js"><code>// Original code import fs from 'node:fs' fs.open <p>// Old output (with --bundle --format=esm --platform=node --target=node18,es2022)<br /> import fs from "fs";<br /> </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.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> <h2>0.23.1</h2> <ul> <li> <p>Allow using the <code>node:</code> import prefix with <code>es*</code> targets (<a href="https://redirect.github.com/evanw/esbuild/issues/3821";>#3821</a>)</p> <p>The <a href="https://nodejs.org/api/esm.html#node-imports";><code>node:</code> prefix on imports</a> is an alternate way to import built-in node modules. For example, <code>import fs from "fs"</code> can also be written <code>import fs from "node:fs"</code>. This only works with certain newer versions of node, so esbuild removes it when you target older versions of node such as with <code>--target=node14</code> so that your code still works. With the way esbuild's platform-specific feature compatibility table works, this was added by saying that only newer versions of node support this feature. However, that means that a target such as <code>--target=node18,es2022</code> removes the <code>node:</code> prefix because none of the <code>es*</code> targets are known to support this feature. This release adds the support for the <code>node:</code> flag to esbuild's internal compatibility table for <code>es*</code> to allow you to use compound targets like this:</p > <pre lang="js"><code>// Original code import fs from 'node:fs' fs.open <p></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/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 => 1.23.1</li> <li>Additional commits viewable in <a href="https://github.com/evanw/esbuild/compare/v0.20.0...v0.24.0";>compare view</a></li> </ul> </details> <br /> [](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> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
