.png%3Falt%3Dmedia%26token%3D325f86f6-2e2a-4d0f-a8c7-b28d4eea56a4){kind=logo}
.png%3Falt%3Dmedia%26token%3D325f86f6-2e2a-4d0f-a8c7-b28d4eea56a4){kind=logo}
Comment on page
Writing Plugins
An Electron Forge Plugin has to export a single class that extends our base plugin. The base plugin can be depended on by installing
@electron-forge/plugin-base. It can implement two methods, neither are required.If implemented this method will be once during plugin initialization inside Forge, this method is called only once and shouldn't result in any side effects being executed. You must return an object in a similar format to
forgeConfig.hooks. i.e. an object map between hook names and an array of hook functions.The possible hook names and the parameters passed to the hook function you return are documented over in the Configuration section of the docs.
export default class MyPlugin extends PluginBase {
getHooks () {
return {
prePackage: [this.prePackage]
};
}
prePackage () {
console.log('running prePackage hook');
}
}
If implemented, this method will be called every time the user runs
electron-forge start, if you return a ChildProcess you can override the built in start logic and Electron Forge will not spawn it's own process, rather it will watch the one you returned. If you return false forge will spawn Electron itself but you could still run custom logic such as started compilation for code or downloading certain binaries before the app starts.Please note that overriding the start logic here only works in development if you want to change how an app runs once packaged you will need to use a build hook to inject code into the packaged app.
export default class MyPlugin extends Pluginbase {
async startLogic (opts) {
await this.compileMainProcess();
return null;
}
compileMainProcess () { /* ... */ }
}
Last modified 5mo ago