Skip to content

fix(deps): update all non-major dependencies#241

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/all-minor-patch
Aug 18, 2025
Merged

fix(deps): update all non-major dependencies#241
renovate[bot] merged 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Aug 18, 2025

This PR contains the following updates:

Package Change Age Confidence
@sxzz/prettier-config ^2.2.3 -> ^2.2.4 age confidence
@types/node (source) ^22.17.1 -> ^22.17.2 age confidence
bumpp ^10.2.2 -> ^10.2.3 age confidence
esbuild ~0.25.8 -> ~0.25.9 age confidence
rollup (source) ^4.46.2 -> ^4.46.3 age confidence
tsdown ^0.14.0 -> ^0.14.1 age confidence
tsx (source) ^4.20.3 -> ^4.20.4 age confidence
unplugin (source) ^2.3.5 -> ^2.3.6 age confidence
vite (source) ^7.1.1 -> ^7.1.2 age confidence

Release Notes

sxzz/prettier-config (@​sxzz/prettier-config)

v2.2.4

Compare Source

No significant changes

    View changes on GitHub
antfu-collective/bumpp (bumpp)

v10.2.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
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.

rollup/rollup (rollup)

v4.46.3

Compare Source

2025-08-18

Bug Fixes
  • Resolve illegal instruction error on arm64 architectures (#​6055)
  • Resolve sourcemap generation performance regression (#​6057)
Pull Requests
rolldown/tsdown (tsdown)

v0.14.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
privatenumber/tsx (tsx)

v4.20.4

Compare Source

unjs/unplugin (unplugin)

v2.3.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
vitejs/vite (vite)

v7.1.2

Compare Source

Bug Fixes
Miscellaneous Chores

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b842920 to 4f4839e Compare August 18, 2025 06:28
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch from 4f4839e to 628a94c Compare August 18, 2025 09:48
@renovate renovate Bot merged commit cf0ed7f into main Aug 18, 2025
8 checks passed
@renovate renovate Bot deleted the renovate/all-minor-patch branch August 18, 2025 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants