dependabot[bot] opened a new pull request, #260: URL: https://github.com/apache/arrow-js/pull/260
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.25.8 to 0.25.9. <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.25.9</h2> <ul> <li> <p>Better support building projects that use Yarn on Windows (<a href="https://redirect.github.com/evanw/esbuild/issues/3131";>#3131</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3663";>#3663</a>)</p> <p>With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the <code>C:</code> drive. The problem was as follows:</p> <ol> <li>Yarn in Plug'n'Play mode on Windows stores its global module cache on the <code>C:</code> drive</li> <li>Some developers put their projects on the <code>D:</code> drive</li> <li>Yarn generates relative paths that use <code>../..</code> to get from the project directory to the cache directory</li> <li>Windows-style paths don't support directory traversal between drives via <code>..</code> (so <code>D:\..</code> is just <code>D:</code>)</li> <li>I didn't have access to a Windows machine for testing this edge case</li> </ol> <p>Yarn works around this edge case by pretending Windows-style paths beginning with <code>C:\</code> are actually Unix-style paths beginning with <code>/C:/</code>, so the <code>../..</code> path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.</p> </li> <li> <p>Preserve parentheses around function expressions (<a href="https://redirect.github.com/evanw/esbuild/issues/4252";>#4252</a>)</p> <p>The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read <a href="https://v8.dev/blog/preparser";>V8's blog post about this</a> for more details.</p> <p>Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:</p> <pre lang="js"><code>// Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }()) <p>// Old output<br /> const fn0 = () => 0;<br /> const fn1 = () => 1;<br /> console.log(fn0, function() {<br /> return fn1();<br /> }());</p> <p>// New output<br /> const fn0 = () => 0;<br /> const fn1 = (() => 1);<br /> console.log(fn0, (function() {<br /> return fn1();<br /> })());<br /> </code></pre></p> <p>Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.</p> </li> <li> <p>Update Go from 1.23.10 to 1.23.12 (<a href="https://redirect.github.com/evanw/esbuild/issues/4257";>#4257</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4258";>#4258</a>)</p> <p>This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.</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.25.9</h2> <ul> <li> <p>Better support building projects that use Yarn on Windows (<a href="https://redirect.github.com/evanw/esbuild/issues/3131";>#3131</a>, <a href="https://redirect.github.com/evanw/esbuild/issues/3663";>#3663</a>)</p> <p>With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the <code>C:</code> drive. The problem was as follows:</p> <ol> <li>Yarn in Plug'n'Play mode on Windows stores its global module cache on the <code>C:</code> drive</li> <li>Some developers put their projects on the <code>D:</code> drive</li> <li>Yarn generates relative paths that use <code>../..</code> to get from the project directory to the cache directory</li> <li>Windows-style paths don't support directory traversal between drives via <code>..</code> (so <code>D:\..</code> is just <code>D:</code>)</li> <li>I didn't have access to a Windows machine for testing this edge case</li> </ol> <p>Yarn works around this edge case by pretending Windows-style paths beginning with <code>C:\</code> are actually Unix-style paths beginning with <code>/C:/</code>, so the <code>../..</code> path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.</p> </li> <li> <p>Preserve parentheses around function expressions (<a href="https://redirect.github.com/evanw/esbuild/issues/4252";>#4252</a>)</p> <p>The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read <a href="https://v8.dev/blog/preparser";>V8's blog post about this</a> for more details.</p> <p>Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:</p> <pre lang="js"><code>// Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }()) <p>// Old output<br /> const fn0 = () => 0;<br /> const fn1 = () => 1;<br /> console.log(fn0, function() {<br /> return fn1();<br /> }());</p> <p>// New output<br /> const fn0 = () => 0;<br /> const fn1 = (() => 1);<br /> console.log(fn0, (function() {<br /> return fn1();<br /> })());<br /> </code></pre></p> <p>Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.</p> </li> <li> <p>Update Go from 1.23.10 to 1.23.12 (<a href="https://redirect.github.com/evanw/esbuild/issues/4257";>#4257</a>, <a href="https://redirect.github.com/evanw/esbuild/pull/4258";>#4258</a>)</p> <p>This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.</p> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/evanw/esbuild/commit/195e05c16f03a341390feef38b8ebf17d3075e14";><code>195e05c</code></a> publish 0.25.9 to npm</li> <li><a href="https://github.com/evanw/esbuild/commit/3dac33f2a2ba60387fb9aaca96b3e80b9e0512e0";><code>3dac33f</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/3131";>#3131</a>, fix <a href="https://redirect.github.com/evanw/esbuild/issues/3663";>#3663</a>: yarnpnp + windows + D drive</li> <li><a href="https://github.com/evanw/esbuild/commit/0f2c5c8c11dc3fa2a4e9e82df202d0b607e59de4";><code>0f2c5c8</code></a> mock fs now supports multiple volumes on windows</li> <li><a href="https://github.com/evanw/esbuild/commit/100a51e791ce714a1a90557bc9e5133fa0d38692";><code>100a51e</code></a> split out yarnpnp snapshot tests</li> <li><a href="https://github.com/evanw/esbuild/commit/13aace38bd1243e440061d1611e90a46ef55029c";><code>13aace3</code></a> remove <code>C:</code> assumption from windows snapshot tests</li> <li><a href="https://github.com/evanw/esbuild/commit/f1f413f18bce15a53fa4251f11a4747be94075e0";><code>f1f413f</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4252";>#4252</a>: preserve parentheses around functions</li> <li><a href="https://github.com/evanw/esbuild/commit/1bc809190bdb68ad27fc0a6e6d385b4f635c90e2";><code>1bc8091</code></a> fix <a href="https://redirect.github.com/evanw/esbuild/issues/4257";>#4257</a>, close <a href="https://redirect.github.com/evanw/esbuild/issues/4258";>#4258</a>: go 1.23.10 => 1.23.12</li> <li><a href="https://github.com/evanw/esbuild/commit/bc52135d02f794f28777c8e00db91997e0d98cab";><code>bc52135</code></a> move the go compiler version to <code>go.version</code></li> <li><a href="https://github.com/evanw/esbuild/commit/a0af5d1037c6e2509531151d153e875093f426b6";><code>a0af5d1</code></a> makefile: use <code>ESBUILD_VERSION</code> consistently</li> <li>See full diff in <a href="https://github.com/evanw/esbuild/compare/v0.25.8...v0.25.9";>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: github-unsubscr...@arrow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
