You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The information posted isn't sufficient to reproduce the issue without a lot of guesswork. There have however been other reports of app incompatibility updating from Node.js 24.15.0 to 24.16.0. In at least two cases, app maintainers were able to fix the incompatibility.
You may get a better response if you check with electron-forge if this is a known issue, and then report it to them if it is not known, with exact repro steps (including the versions you are using) so that they may possibly be able to advise you.
There have however been other reports of app incompatibility updating from Node.js 24.15.0 to 24.16.0. In at least two cases, app maintainers were able to fix the incompatibility.
This is the Node.js issue tracker, consider reporting that to electron-forge instead.
yes, but this strange that minor update broken smth. maybe backward-compability was broken.
yes, but this strange that minor update broken smth. maybe backward-compability was broken.
I have come across several packages that stopped working with Node.js 24.16.0. In your situation I would check that you're using the latest available electron-forge, and if you still have a problem, then make sure you report it to electron-forge.
@electron-forge/cli@7.11.2 uses extract-zip@2.0.1 which is the dependency causing compatibility issues in other packages.
If that is the package that you are using.
Activity
long76 commentedon May 26, 2026
seems broken
cwd/pwdin 24.16.0MikeMcC399 commentedon May 26, 2026
The information posted isn't sufficient to reproduce the issue without a lot of guesswork. There have however been other reports of app incompatibility updating from Node.js 24.15.0 to 24.16.0. In at least two cases, app maintainers were able to fix the incompatibility.
You may get a better response if you check with electron-forge if this is a known issue, and then report it to them if it is not known, with exact repro steps (including the versions you are using) so that they may possibly be able to advise you.
aduh95 commentedon May 26, 2026
This is the Node.js issue tracker, consider reporting that to electron-forge instead.
long76 commentedon May 26, 2026
yes, but this strange that minor update broken smth. maybe backward-compability was broken.
MikeMcC399 commentedon May 27, 2026
I have come across several packages that stopped working with Node.js 24.16.0. In your situation I would check that you're using the latest available
electron-forge, and if you still have a problem, then make sure you report it toelectron-forge.MikeMcC399 commentedon May 27, 2026
@electron-forge/cli@7.11.2usesextract-zip@2.0.1which is the dependency causing compatibility issues in other packages.If that is the package that you are using.
electron-forgethat you referred to is deprecatedlong76 commentedon May 27, 2026
yes, i use
@electron-forge/cli@7.11.2long76 commentedon May 27, 2026
made repository
https://github.com/long76/build_bug
Steps
package forever
long76 commentedon May 27, 2026
long76 commentedon May 27, 2026
electron/forge#4277
long76 commentedon May 27, 2026
yeap, you are right, they confirm it.
but first task registered in
electronrepoMikeMcC399 commentedon May 27, 2026
Well done for getting the confirmation from the Electron team!