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
I agree to follow the code of conduct that this project uses.
I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Problem description
In Electron, Fuses are package-time toggle features that can disable certain features on a per-app basis. For example, apps might not want to ship with the ELECTRON_RUN_AS_NODE capability, and can turn it off for their app with a fuse.
Going for a plugin would potentially help with modularization, though it doesn't look like it's going to take a lot of code (@electron/fuses' docs show a complete example in just a few LOC), so maybe it can be just built into Forge (or packager?) directly. Either way, I'd happy to take on this once an approach is decided.
@erikian Why close that PR? It looked perfect for adding Fuses support in both places. Has anyone made a plugin to do support using Fuses through Forge/Packager yet?
Pre-flight checklist
Problem description
In Electron, Fuses are package-time toggle features that can disable certain features on a per-app basis. For example, apps might not want to ship with the
ELECTRON_RUN_AS_NODE
capability, and can turn it off for their app with a fuse.See https://www.electronjs.org/docs/latest/tutorial/fuses
Proposed solution
Forge should include a way to easily configure fuses in the packaging process.
Alternatives considered
This can be implemented in various manners in the Forge process, and we don't really have existing guidelines on which one is better:
Additional information
No response
The text was updated successfully, but these errors were encountered: