CLI: Include electron-builder configuration over the electron.manifest.json #30

Closed
opened 2026-01-29 16:27:51 +00:00 by claunia · 10 comments
Owner

Originally created by @GregorBiswanger on GitHub (Oct 24, 2017).

Originally assigned to: @robertmuehsig on GitHub.

The electron-builder supports a build configuration through the package.json.
We need to inlcude a default configuration in the electron.manifest.json, that based on the electron-builder build configuration.

Maybe we can include an assets folder with sample images? ("electronize init").

Information about the electron-builder configuration:
https://github.com/electron-userland/electron-builder/blob/master/docs/configuration/configuration.md

http://electron.rocks/electron-builder-explained/

Originally created by @GregorBiswanger on GitHub (Oct 24, 2017). Originally assigned to: @robertmuehsig on GitHub. The electron-builder supports a build configuration through the package.json. We need to inlcude a default configuration in the electron.manifest.json, that based on the electron-builder build configuration. Maybe we can include an assets folder with sample images? ("electronize init"). Information about the electron-builder configuration: https://github.com/electron-userland/electron-builder/blob/master/docs/configuration/configuration.md http://electron.rocks/electron-builder-explained/
claunia added the Feature label 2026-01-29 16:27:51 +00:00
Author
Owner

@robertmuehsig commented on GitHub (Oct 25, 2017):

Could you share a sample configuration? I'm not sure how to apply those config values :/

@robertmuehsig commented on GitHub (Oct 25, 2017): Could you share a sample configuration? I'm not sure how to apply those config values :/
Author
Owner

@GregorBiswanger commented on GitHub (Oct 25, 2017):

"build": { "appId": "com.jamzi.quickstart", "win": { "target": "nsis", "icon": "build/icon.ico" } }

See here too:
https://medium.com/@jamzi/building-desktop-applications-with-electron-electron-builder-47484193cbcc

@GregorBiswanger commented on GitHub (Oct 25, 2017): ` "build": { "appId": "com.jamzi.quickstart", "win": { "target": "nsis", "icon": "build/icon.ico" } } ` See here too: https://medium.com/@jamzi/building-desktop-applications-with-electron-electron-builder-47484193cbcc
Author
Owner

@robertmuehsig commented on GitHub (Nov 8, 2017):

What is "nsis"? Can we use this to configure App Title names / icons for the different platforms?

@robertmuehsig commented on GitHub (Nov 8, 2017): What is "nsis"? Can we use this to configure App Title names / icons for the different platforms?
Author
Owner

@GregorBiswanger commented on GitHub (Nov 8, 2017):

Good question. I don't know...

@GregorBiswanger commented on GitHub (Nov 8, 2017): Good question. I don't know...
Author
Owner

@yoDon commented on GitHub (Nov 18, 2017):

Is this the right place to ask about how to add additional assets/resources to the build process?

I ran into the need for additional assets/resources as kind of a blocker while working on the Electron.NET-React-Typescript-MobX boilerplate as described here.

@yoDon commented on GitHub (Nov 18, 2017): Is this the right place to ask about how to add additional assets/resources to the build process? I ran into the need for additional assets/resources as kind of a blocker while working on the Electron.NET-React-Typescript-MobX boilerplate as described [here](https://github.com/yoDon/Electron.NET-React-Typescript-MobX/#hack-hack-hack-begin).
Author
Owner

@DrSensor commented on GitHub (Feb 5, 2018):

+1 for supporting electron-builder because it has more features (e.g injecting auto-updater and etc) than electron-packager

One of use case that I need electron-builder is to package my app into snap then deploy it to arm device for kiosk app.

@DrSensor commented on GitHub (Feb 5, 2018): > `+1` for supporting `electron-builder` because it has more features (e.g injecting auto-updater and etc) than `electron-packager` One of use case that I need `electron-builder` is to package my app into [snap](https://snapcraft.io) then deploy it to arm device for kiosk app.
Author
Owner

@robertmuehsig commented on GitHub (Feb 6, 2018):

Electron-builder is a more advanced electron packer? (my electron knowledge is pretty low :/)

@robertmuehsig commented on GitHub (Feb 6, 2018): Electron-builder is a more advanced electron packer? (my electron knowledge is pretty low :/)
Author
Owner

@DrSensor commented on GitHub (Feb 6, 2018):

My opinion is biased because previously I build desktop app with electron-vue and I need some features of electron-builder have (mainly packaging for many linux distros, CI support, and auto add-build SQLite module). Maybe this short section doc can explain better.

The most compelling feature (although never use it) is auto updater. This feature open possibility to release 2 or more different version app (e.g stable and nightly.build) using staged rollouts.

@DrSensor commented on GitHub (Feb 6, 2018): My opinion is biased because previously I build desktop app with [electron-vue](https://github.com/SimulatedGREG/electron-vue) and I need some features of electron-builder have (mainly packaging for many linux distros, CI support, and auto add-build SQLite module). Maybe this short [section doc](https://simulatedgreg.gitbooks.io/electron-vue/content/en/building_your_app.html) can explain better. The most compelling feature (although never use it) is [auto updater](https://simulatedgreg.gitbooks.io/electron-vue/content/en/using-electron-builder.html). This feature open possibility to release 2 or more different version app (e.g stable and nightly.build) using [staged rollouts](https://www.electron.build/auto-update#staged-rollouts).
Author
Owner

@robertmuehsig commented on GitHub (Feb 19, 2018):

We released a new version and now support addional params from electron-packager, e.g. we can now execute something like this:
build /target custom win7-x86;win32 /dotnet-configuration Debug /electron-arch ia32 /electron-params "--prune=true "

Via the /electron-params a user can just tunnel the desired commands directly to the electron-packager.

Please give feedback to this feature. I'm not sure if this will solve any problem, but maybe this is a start :)

@robertmuehsig commented on GitHub (Feb 19, 2018): We released a new version and now support addional params from electron-packager, e.g. we can now execute something like this: build /target custom win7-x86;win32 /dotnet-configuration Debug /electron-arch ia32 /electron-params "--prune=true " Via the /electron-params a user can just tunnel the desired commands directly to the electron-packager. Please give feedback to this feature. I'm not sure if this will solve any problem, but maybe this is a start :)
Author
Owner

@DrSensor commented on GitHub (Apr 17, 2018):

Would you reference which commit or PR for that feature?

@DrSensor commented on GitHub (Apr 17, 2018): Would you reference which commit or PR for that feature?
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/Electron.NET#30