Electron Fuses via app-builder-lib is v1.8.0, causes mismatch with the number of available Fuses (`strictlyRequireAllFuses`)

[danielweck]

Following #6365

I am seeing this error in my build since Electron v41, likely because of the introduction of a new Fuse (now 9 in total):

https://github.com/electron/fuses/blob/12810c24e192a30f56ff295ee5f6e544ed4670b9/src/index.ts#L103

strictlyRequireAllFuses: The fuse wire in the Electron binary has ${fuseWireLength} fuses but you only provided a config for ${wire.length} fuses, you may need to update @electron/fuses or provide additional fuse settings

See:

electron-builder/packages/app-builder-lib/src/platformPackager.ts

Lines 413 to 428 in ed422f3

	public addElectronFuses(context: AfterPackContext, fuses: FuseConfig) {
	const { appOutDir, electronPlatformName } = context
	const ext = {
	darwin: ".app",
	mas: ".app",
	win32: ".exe",
	linux: "",
	}[electronPlatformName]
	const executableName = this instanceof LinuxPackager ? this.executableName : this.appInfo.productFilename
	const electronBinaryPath = path.join(appOutDir, `${executableName}${ext}`)
	log.info({ electronPath: log.filePath(electronBinaryPath) }, "executing @electron/fuses")
	return flipFuses(electronBinaryPath, fuses)
	}

Culprit, v1.x:

electron-builder/packages/app-builder-lib/package.json

Line 52 in ed422f3

"@electron/fuses": "^1.8.0",

... but now at v2.x:

https://github.com/electron/fuses/releases

[mmaietta]

Thanks for the ping! So, in order to update electron/fuses in this project, the entire project needs to be converted to ESM which is intended for v27. I had to put a pause on the work though but intend to return to it soon.

You can track here #9483

[danielweck]

related issue: #9770

[danielweck]

Just in case this helps issue tracker visitors: you can invoke the most recent version of @electron/fuses via the afterPack hook, just as the latest revision of @electron/notarize can be used from the afterSign hook.