chore(deps): update dependency esbuild to v0.25.9 #2566

Merged
group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 merged 1 commits from renovate/esbuild-0.x into main 2025-08-13 07:08:47 +00:00
group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented 2025-08-13 00:05:31 +00:00 (Migrated from gitlab.com)

This MR contains the following updates:

Package Change Age Confidence
esbuild 0.25.8 -> 0.25.9 age confidence

Release Notes

evanw/esbuild (esbuild)

v0.25.9

Compare Source

  • Better support building projects that use Yarn on Windows (#​3131, #​3663)

    With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

    1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive
    2. Some developers put their projects on the D: drive
    3. Yarn generates relative paths that use ../.. to get from the project directory to the cache directory
    4. Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)
    5. I didn't have access to a Windows machine for testing this edge case

    Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. 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.

  • Preserve parentheses around function expressions (#​4252)

    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 V8's blog post about this for more details.

    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:

    // Original code
    const fn0 = () => 0
    const fn1 = (() => 1)
    console.log(fn0, function() { return fn1() }())
    
    // Old output
    const fn0 = () => 0;
    const fn1 = () => 1;
    console.log(fn0, function() {
      return fn1();
    }());
    
    // New output
    const fn0 = () => 0;
    const fn1 = (() => 1);
    console.log(fn0, (function() {
      return fn1();
    })());
    

    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.

  • Update Go from 1.23.10 to 1.23.12 (#​4257, #​4258)

    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.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.


  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot.

This MR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [esbuild](https://github.com/evanw/esbuild) | [`0.25.8` -> `0.25.9`](https://renovatebot.com/diffs/npm/esbuild/0.25.8/0.25.9) | [![age](https://developer.mend.io/api/mc/badges/age/npm/esbuild/0.25.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/esbuild/0.25.8/0.25.9?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>evanw/esbuild (esbuild)</summary> ### [`v0.25.9`](https://github.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0259) [Compare Source](https://github.com/evanw/esbuild/compare/v0.25.8...v0.25.9) - Better support building projects that use Yarn on Windows ([#&#8203;3131](https://github.com/evanw/esbuild/issues/3131), [#&#8203;3663](https://github.com/evanw/esbuild/issues/3663)) With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the `C:` drive. The problem was as follows: 1. Yarn in Plug'n'Play mode on Windows stores its global module cache on the `C:` drive 2. Some developers put their projects on the `D:` drive 3. Yarn generates relative paths that use `../..` to get from the project directory to the cache directory 4. Windows-style paths don't support directory traversal between drives via `..` (so `D:\..` is just `D:`) 5. I didn't have access to a Windows machine for testing this edge case Yarn works around this edge case by pretending Windows-style paths beginning with `C:\` are actually Unix-style paths beginning with `/C:/`, so the `../..` 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. - Preserve parentheses around function expressions ([#&#8203;4252](https://github.com/evanw/esbuild/issues/4252)) 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 [V8's blog post about this](https://v8.dev/blog/preparser) for more details. 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: ```js // Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }()) // Old output const fn0 = () => 0; const fn1 = () => 1; console.log(fn0, function() { return fn1(); }()); // New output const fn0 = () => 0; const fn1 = (() => 1); console.log(fn0, (function() { return fn1(); })()); ``` 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. - Update Go from 1.23.10 to 1.23.12 ([#&#8203;4257](https://github.com/evanw/esbuild/issues/4257), [#&#8203;4258](https://github.com/evanw/esbuild/pull/4258)) 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. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS42Ni4wIiwidXBkYXRlZEluVmVyIjoiNDEuNjYuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented 2025-08-13 00:05:33 +00:00 (Migrated from gitlab.com)

restored source branch renovate/esbuild-0.x

restored source branch `renovate/esbuild-0.x`
group_2759636_bot_1c34751f7eccad09e089ac15ee7bd902 commented 2025-08-13 00:05:34 +00:00 (Migrated from gitlab.com)

mentioned in issue #49

mentioned in issue #49
argoyle commented 2025-08-13 07:08:24 +00:00 (Migrated from gitlab.com)

added 2 commits

  • e2ea3446 - 1 commit from branch main
  • 21828f02 - chore(deps): update dependency esbuild to v0.25.9

Compare with previous version

added 2 commits <ul><li>e2ea3446 - 1 commit from branch <code>main</code></li><li>21828f02 - chore(deps): update dependency esbuild to v0.25.9</li></ul> [Compare with previous version](/unboundsoftware/dancefinder/dancefinder-app/-/merge_requests/2517/diffs?diff_id=1456311143&start_sha=6bc68d20d5d7c6b3e5bc0313e936bdfbc399a956)
argoyle (Migrated from gitlab.com) merged commit into main 2025-08-13 07:08:47 +00:00
Sign in to join this conversation.