Bringing Electron applications to millions of Linux users

by Alan Pope on 26 July 2018

Electron is one of the most popular frameworks for creating cross-platform desktop applications right now. Many developers use electron-builder to do the heavy-lifting of package management for their Electron apps.

electron-builder has support for creating snap packages out of the box. Bringing your Electron desktop app to Linux can be as simple as a one-line change in your package.json. Here we’ll use an existing application – BitWarden – to show you how.

BitWarden is a cross-platform password store featuring secure cloud sync across their desktop and mobile clients. The desktop client is available for Linux in the snap store.

The source for BitWarden is on GitHub, but that’s not a requirement for building snaps. It just makes it easier for us to point out how they implemented the snap build. BitWarden are currently using electron builder 20.8.1 or later,

"devDependencies": {
"electron-builder": "^20.8.1",

In the "linux" section of the package.json the BitWarden developers added a 'snap' build target. This is alongside the other build targets the developers have chosen to support.

"linux": {
"category": "Utility",
"synopsis": "A secure and free password manager for all of your devices.",
"target": [

For many electron applications this one line is enough to generate a working snap! Simply build as you normally do either locally or using a remote service such as Travis or CircleCI and this will produce a snap.

electron-builder exposes additional snap features via an optional 'snap' stanza in the package.json. For example the BitWarden application requires an additional interface to access the password management service, and an additional package to be staged inside the snap.

Interfaces are comprised of plugs and slots at each end, so the term ‘plugs’ allows you to specify a list of interfaces you want to enable in the snap. The 'stagePackages' section allows you to specify debs from the Ubuntu 16.04 archive which will be pulled into the snap at build time.

"snap": {
"confinement": "strict",
"plugs": [
"stagePackages": [

That’s it! The full package.json can be found in the BitWarden GitHub repo.

The community of developers building snap, snapcraft and snaps hang out on the snapcraft forums. Join us!

Newsletter Signup

Related posts

How’s my snap faring on different distributions?

The life of an application can roughly be divided into two: everything that happens before it goes live – building, packaging, publication – and then, everything that happens after that milestone. Traditionally, on Linux, developers didn’t always have an easy way of deriving useful numbers on how their software was doing across the distro […]

What has snapd ever done for other distros?

Snaps are self-contained applications designed with ease of use, security and portability in mind. They bundle their necessary dependencies, so they can work and run without modifications across numerous Linux distributions. How many? More than 40. Yet, often when technology is strongly associated with a particular product, in this case s […]

The magic behind snap interfaces

Snaps are confined, self-contained applications, designed with portability and security in mind. By default, strictly confined snaps run in isolation, with minimal access to system resources. For instance, they cannot access home, network, audio, or display. To make their snaps usable, developers and publishers can declare a set of interf […]