Skip to content

Electron

Tip

The tutorial shows you how to generate and package a simple Electron app.

Overview

There are several packaging tools and update engines that can be used with Electron, however they all have a variety of problems:

Conveyor uses native updates on Windows/Linux, Sparkle 2 on macOS, and regular HTTP servers.

The other standard features of Conveyor can also eliminate hassle:

  • No need to find machines for each target OS to build packages. You can make packages for every OS on your laptop.
  • Use more convenient config syntax and features than raw JSON.
  • Handles all the details of code signing without native tools, which are often awkward to use.
  • Can self-sign if you don't want to use signing keys. Other tools make unsigned apps if you don't have keys, but these don't integrate with the host operating system as well.
  • You get a self-contained download site with HTML that detects your users operating system and CPU.
  • It's fully documented.

Conveyor treats Electron apps mostly the same as native apps, meaning that no code changes are necessary to get working software updates.

Synopsis

A basic conveyor.conf looks like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
// You must import the electron stdlib config.
include required("/stdlib/electron/electron.conf")

// You must also import your package-lock.json file.
// Defaults will be set from it.
package-lock {
    include required("package-lock.json") 
}

// Override the Electron version. By default this comes from package-lock.json 
app.electron.version = 19.0.1

// If necessary change where it's downloaded from. The default is GitHub:
app.electron.download-base-url = github.com/electron/electron/releases/download/

Keys

app.electron.version If set then this config is for an Electron app, and this is the version of Electron to bundle.

app.electron.download-base-url Where to find Electron builds to download. The URLs are composed like this: 

1
${app.electron.download-base-url}/v${app.electron.version}/electron-v${app.electron.version}-$os-$cpu.zip

so they must follow the same layout as that used on GitHub. You can specify a file: URL here if necessary.

App resources

The stdlib electron.conf file will import the following files to your resources/app directory:

  • *.json
  • *.js
  • *.css
  • *.html
  • The node_modules directory.

You can add more inputs or replace the default set like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
app {
    // Add more top level files.
    inputs += "*.ts"

    // Add a  directory preserving the placement. 
    // (otherwise, the contents are copied to the top level).
    inputs += node_modules -> node_modules

    // Replace the inputs entirely.
    inputs = [ "app.asar" ]
}

Caveats

Be aware of the following caveats:

  • There's no API to control or monitor updates yet. Note that such an API doesn't necessarily make sense on some platforms e.g. Linux where the user's package manager will apply updates, or on Windows where the app can be updated silently in the background when it's not running.
  • It has only been tested with Electron 19 and 20. Conveyor replaces the entry point binary and thus must be synchronized with Electron releases.
  • Conveyor doesn't make ASAR files at the moment, so all files will be shipped unpacked. If your app consists of very large numbers of small files this may reduce performance. You could use a bundler, or make an asar file yourself and supply it as an input to work around this limitation.