A complete solution to package and build a ready for distribution Electron, Proton Native app for macOS, Windows and Linux with “auto update” support out of the box. :shipit:
Always looking for community contributions! 👀 Setting up a dev environment is easy to do 🪩
See the full documentation on electron.build.
7z
, zip
, tar.xz
, tar.7z
, tar.lz
, tar.gz
, tar.bz2
, dir
(unpacked directory).dmg
, pkg
, mas
.deb
), rpm
, freebsd
, pacman
, p5p
, apk
.nsis
(Installer), nsis-web
(Web installer), portable
(portable app without installation), AppX (Windows Store), MSI, Squirrel.Windows.Question | Answer |
---|---|
“I want to configure electron-builder” | See options |
“I found a bug or I have a question” | Open an issue |
“I want to support development” | Donate |
Yarn is strongly recommended instead of npm.
yarn add electron-builder --dev
In order to use with pnpm
, you'll need to adjust your .npmrc
to use any one the following approaches in order for your dependencies to be bundled correctly (ref: #6389):
node-linker=hoisted
public-hoist-pattern=*
shamefully-hoist=true
Note: Setting shamefully-hoist to true is the same as setting public-hoist-pattern to *.
Yarn 3 use PnP by default, but electron-builder still need node-modules(ref: yarnpkg/berry#4804). Add configuration in the .yarnrc.yaml
as follows:
nodeLinker: "node-modules"
will declare to use node-modules instead of PnP.
electron-webpack-quick-start is a recommended way to create a new Electron application. See Boilerplates.
Specify the standard fields in the application package.json
— name, description
, version
and author.
Specify the build configuration in the package.json
as follows:
"build": {
"appId": "your.id",
"mac": {
"category": "your.app.category.type"
}
}
See all options. Option files to indicate which files should be packed in the final application, including the entry file, maybe required.
You can also use separate configuration files, such as js
, ts
, yml
, and json
/json5
. See read-config-file for supported extensions. JS Example for programmatic API
Add icons.
Add the scripts key to the development package.json
:
"scripts": {
"app:dir": "electron-builder --dir",
"app:dist": "electron-builder"
}
Then you can run yarn app:dist
(to package in a distributable format (e.g. dmg, windows installer, deb package)) or yarn app:dir
(only generates the package directory without really packaging it. This is useful for testing purposes).
To ensure your native dependencies are always matched electron version, simply add script "postinstall": "electron-builder install-app-deps"
to your package.json
.
If you have native addons of your own that are part of the application (not as a dependency), set nodeGypRebuild to true
.
Please note that everything is packaged into an asar archive by default.
For an app that will be shipped to production, you should sign your application. See Where to buy code signing certificates.
See node_modules/electron-builder/out/index.d.ts
. Typings for TypeScript are provided and also can be found here.
Code snippet provided below is also shown "in action" here as well.
"use strict"
const builder = require("electron-builder")
const Platform = builder.Platform
// Promise is returned
builder.build({
targets: Platform.MAC.createTarget(),
config: {
"//": "build options, see https://goo.gl/QQXmcV"
}
})
.then(() => {
// handle result
})
.catch((error) => {
// handle error
})
Set the DEBUG
environment variable to debug what electron-builder is doing:
DEBUG=electron-builder
FPM_DEBUG
env to add more details about building linux targets (except snap and appimage).
DEBUG_DMG=true
env var to add more debugging/verbosity from hdiutil
(macOS).
!!! tip "cmd" On Windows the environment variable is set using the set command.
set DEBUG=electron-builder
!!! tip "PowerShell" PowerShell uses different syntax to set environment variables.
$env:DEBUG=electron-builder
We do this open source work in our free time. If you'd like us to invest more time on it, please donate.