npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@davidwinter/electron-forge-maker-snap

v2.0.7

Published

[![test](https://github.com/davidwinter/electron-forge-maker-snap/workflows/test/badge.svg)](https://github.com/davidwinter/electron-forge-maker-snap/actions?query=workflow%3Atest) [![Codecov](https://img.shields.io/codecov/c/github/davidwinter/electron-f

Readme

@davidwinter/electron-forge-maker-snap

test Codecov npm (scoped) npm

Simple snap packaging for electron-forge that just works

Prerequisites

  • Ensure that snapcraft is installed via snap (the .deb version of snap is now deprecated)

Installation

yarn add @davidwinter/electron-forge-maker-snap --dev

or

npm install @davidwinter/electron-forge-maker-snap --dev

Usage

You can read more about Makers config on the electron-forge website, but essentially the config required is:

{
	name: '@davidwinter/electron-forge-maker-snap',
	config: {
		categories: ['Utility']
		// See below for more configuration options
	}
}

Then make your snap package:

electron-forge make --target="@davidwinter/electron-forge-maker-snap"

Once completed, the snap package will be located at: out/make with a filename like {executable}-{version}.snap, for example, out/make/nimblenote-2.0.3.snap.

Using with CI

When using this maker with CI, such as GitHub Actions, CircleCI etc, it is best practice to tell snapcraft to build snaps in the host build environment. To do this, set the environment variable SNAP_BUILD_ENVIRONMENT=host.

An example that works with GitHub Actions:

- name: Install snapcraft
  run: sudo snap install snapcraft --classic

- name: Build snap package
  run: yarn make
  env:
    SNAPCRAFT_BUILD_ENVIRONMENT: host

- name: Upload snap artifact
  uses: actions/upload-artifact@v2
  with:
    path: out/make/*.snap

Debugging

Run with DEBUG='electron-forge-maker-snap:*,electron-forge:lifecycle' for debug output from snapcraft:

DEBUG='electron-forge-maker-snap:*,electron-forge:lifecycle' electron-forge make --target="@davidwinter/electron-forge-maker-snap"

Appending the ,electron-forge:lifecycle debug namespace above is required in order to see this makers debug output. Otherwise by default, during the electron-forge output, any other debug messages are suppressed so that it doesn't interfere with the CLI interface. Adding this additional namespace acts as a flag to enable the debug output in a safe way.

Configuration

The maker will try and figure out a bunch of sensible defaults for your config, but the following values can be overridden.

applicationName

Type: string
Default: From the derived appName value from the electron-forge configuration.

Maximum length of 40 characters.

This is the human friendly name of the application, also the title that will be used for the Snapstore and .desktop integration with Linux distributions.

Example: Acme Notes 3

executableName

Type: string
Default: A sanatised version of applicationName with invalid characters removed and spaces replaced with dashes.

Can only contain letters in lower case, numbers, and hyphens, and it can’t start or end with a hyphen. Automatic sanitation will be applied.

Example: acme-notes-3

confinement

Type: string
Default: strict

The snap confinement can be either strict, devmode or classic.

grade

Type: string
Default: stable

The snap grade can be either stable or devel.

summary

Type: string
Default: Derived from description within package.json.

Maximum length of 78 characters.

This is used by the Snap Store as the application summary and is mandatory.

Example: Write your best notes with Acme Notes v3!

description

Type: string
Default: Derived from description within package.json.

This can be a multi-line description of the application and is used by the Snap Store.

license

Type: string
Default: Derived from license within package.json.

A license for the snap in the form of an SPDX expression for the license.

Example: MIT

icon

Type: string
Default: Derived from icon within your electron-forge packagerConfig, appending a .png extension if required.

The application icon used within the Snap Store and also with the Linux distribution desktop integration via the .desktop file - what appears in menus and docks.

Example: ./build/icon.png

categories

Type: array of string
Default: []

These categories define which menus the application belongs to on a Linux distribution. See: https://specifications.freedesktop.org/menu-spec/latest/apa.html#main-category-registry

Example: ['Utility', 'Development']

stagePackages

Type: array of string
Default: ['libnss3', 'libnspr4', 'libasound2', 'libgconf2-4', 'libnotify4', 'libpcre3', 'libpulse0', 'libxss1', 'libxtst6']

List of additional packages required to support creationg of the app. If you want to add packages in addition to the default, add an item named default, for example: ['default', 'libxfixes3'].

plugs

Type: array of string
Default: ['alsa', 'browser-support', 'desktop', 'desktop-legacy', 'gsettings', 'home', 'network', 'opengl', 'pulseaudio', 'unity7', 'wayland', 'x11']

List of additional plugs to include in the snap. If you want to add plugs in addition to the default, add an item named default, for example: ['default', 'media-hub'] to add the media-hub plug in addition to all of the defaults.

layout

Type: object

See Snap layouts. Define in the same format described on that page.