### Self-service - [x] I'd be willing to implement a fix ### Describe the bug Related: - https://github.com/yarnpkg/berry/pull/7070 - https://github.com/yarnpkg/berry/issues/7065 Node recently released 24.15.0 and it looks like the changes that broke ^25.7 is also ported to ^24.15 https://github.com/nodejs/node/releases/tag/v24.15.0 Locking our pipeline to 24.14.1 seems to temporarily fix the problem (was using `nvm use 24`, which always pull the latest) ### To reproduce Same reproduction as before: ``` yarn init && yarn add -D eslint && yarn eslint ``` ### Environment ```shell System: OS: Windows 11 10.0.26200 CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-13620H Binaries: Node: 24.15.0 Yarn: 4.12.0 npm: 11.12.1 bun: 1.3.5 Deno: 2.6.4 ``` ### Additional context _No response_
Self-service
Describe the bug
Related:
Node recently released 24.15.0 and it looks like the changes that broke ^25.7 is also ported to ^24.15
https://github.com/nodejs/node/releases/tag/v24.15.0
Locking our pipeline to 24.14.1 seems to temporarily fix the problem (was using
nvm use 24, which always pull the latest)To reproduce
Same reproduction as before:
Environment
System: OS: Windows 11 10.0.26200 CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-13620H Binaries: Node: 24.15.0 Yarn: 4.12.0 npm: 11.12.1 bun: 1.3.5 Deno: 2.6.4Additional context
No response