zulip-electron (two package.json) and onshape-desktop-shell (one package.json) are some real-world projects that use electron-builder for their packaging. Electron Packager is a command line tool and Node. I would use a general case tool instead such as the Free and Open Source Windows Installer XML Toolset aka WiX. On Linux - $ npm run dist |- appname-version.AppImage |- b |- linux-unpackedĮlectron-builder is highly configurable. Electron's windows installer packager strikes me a specific case tool that would likely hit limitations in scenarios like this. On Windows - # When using target - Squirrel $ npm run dist |- win | |- REALESES | |- appnameSetupversion.exe | |- appname-version-full.nupkg |- win-unpacked # When using target - NSIS $ npm run dist |- win | |- appnameSetupversion.exe |- win-unpacked /pathtopackagedappfolder/yourapp.app nameoftheinstaller -overwrite You can now run any of the above commands in the terminal, and it creates you an installer. running it on OSX will create - $ npm run dist |- mac | |- appname-version-mac.zip | |- appname-version.dmg | |- appname.app Our code updates of new release deployment is reflecting fine in our electron desktop app but issue is we have updated main.js which has electron configuration and changes are not reflecting like we added few options on right.

By default build command will only generate the installer for current platform and current arch. The top-level nsis key contains set of options instructing electron-builder on how it should build NSIS target (default target for Windows). We have angular app of which we have created desktop version using electron and installer is created through winstaller. To package your app into an installer use command: npm run dist You’ve successfully configured electron-builder. On windows build you can also use NSIS target which is the default one and recommended by electron-builder.

Electron installer