fix(deps): lock file maintenance all non-major #1625

renovate · 2025-08-11T01:48:59Z

This PR contains the following updates:

Package	Type	Update	Change
		lockFileMaintenance	All locks refreshed
@eslint/js (source)	devDependencies	minor	`9.32.0` -> `9.33.0`
@types/node (source)	devDependencies	patch	`22.17.0` -> `22.17.2`
actions/cache	action	patch	`v4.2.3` -> `v4.2.4`
esbuild	devDependencies	patch	`0.25.8` -> `0.25.9`
eslint (source)	devDependencies	minor	`9.32.0` -> `9.33.0`
fs-extra	dependencies	patch	`11.3.0` -> `11.3.1`
tsx (source)	devDependencies	patch	`4.20.3` -> `4.20.4`
typescript-eslint (source)	devDependencies	minor	`8.39.0` -> `8.40.0`

🔧 This Pull Request updates lock files to use the latest dependency versions.

Release Notes

eslint/eslint (@eslint/js)

`v9.33.0`

Compare Source

actions/cache (actions/cache)

`v4.2.4`

Compare Source

What's Changed

Update README.md by @nebuk89 in https://github.com/actions/cache/pull/1620
Upgrade @actions/cache to 4.0.5 and move @protobuf-ts/plugin to dev depdencies by @Link- in https://github.com/actions/cache/pull/1634
Prepare release 4.2.4 by @Link- in https://github.com/actions/cache/pull/1636

New Contributors

@nebuk89 made their first contribution in https://github.com/actions/cache/pull/1620

Full Changelog: actions/cache@v4...v4.2.4

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.