Patching electron-forge with recent fix

[lethal badger]

I have an existing project that's suffering from the problem described at https://github.com/electron/forge/issues/3549 and I'd like to use the fix for it shown at https://github.com/electron/forge/pull/3592 without having to wait for it to be released. Does anyone have any suggestions about how I can either patch the electron-forge installed with my project or get my project to use a local copy of electron-forge? I tried the 'yarn link' technique described under "Running Forge Locally" at https://github.com/electron/forge/blob/main/CONTRIBUTING.md and also tried removing my installed electron-forge libraries and re-installing them using a copy of electron-forge I checked out (I'd really prefer to avoid this), but neither of those actually solved the problem. In both cases when I ran 'npm run make' (or 'yarn run make') I still got the error, just as though I was still running with the release version of electron-forge. This happens on macOS Ventura 13.6 with node 20.10.0 and electron 28.1.2.

[waxen sand]

Unless I'm missing something, this fix only seems about updating the library @electron/asar. So it should be fairly easy for you to get the fix, you just need to use the latest version of this lib. You can try overrides in your package.json:

"overrides": {
  "@electron/asar": "3.2.10"
}