npmpackage.info

Gathering detailed insights and metrics for electron-builder-squirrel-windows

Gathering detailed insights and metrics for electron-builder-squirrel-windows

electron-builder-squirrel-windows - 26.0.12 | npmpackage.info

electron-builder-squirrel-windows

A complete solution to package and build a ready for distribution Electron app with “auto update” support out of the box

26.0.12

14,180

MIT

TypeScript

32.30 kB

Installations

npm install electron-builder-squirrel-windows

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

22.14.0

NPM Version

10.9.2

Pull Requests

Open

15

Total

2,036

Closed

450

Merged

1,571

Issues

Open

256

Total

7,022

Closed

6,766

Releases

904

v26.0.18

Updated on Jul 08, 2025

electron-updater@6.6.6

electron-updater@6.6.6

Updated on Jul 08, 2025

v26.0.17

Updated on Jun 15, 2025

v26.0.16

Updated on Jun 02, 2025

electron-updater@6.6.5

electron-updater@6.6.5

Updated on Jun 02, 2025

v26.0.15

Updated on May 04, 2025

View All 904 releases

Languages

7

TypeScript

NSIS

JavaScript

Shell

Dockerfile

Smarty

CSS

TypeScript (91.25%)

NSIS (6.27%)

JavaScript (1.59%)

Shell (0.51%)

Dockerfile (0.34%)

Smarty (0.02%)

CSS (0.02%)

Developer

electron-userland

Download Statistics

Total Downloads

0

Last Day

0

Last Week

0

Last Month

0

Last Year

0

GitHub Statistics

MIT License

14,180 Stars

3,408 Commits

1,795 Forks

148 Watchers

80 Branches

570 Contributors

Updated on Jul 12, 2025

Maintainers

2

View All 570 Contributors

Package Meta Information

Latest Version

26.0.12

Package Id

electron-builder-squirrel-windows@26.0.12

Unpacked Size

32.30 kB

Size

7.83 kB

File Count

7

NPM Version

10.9.2

Node Version

22.14.0

Published on

Mar 22, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

0%

NaN

Compared to previous day

Last Week

0%

NaN

Compared to previous week

Last Month

0%

NaN

Compared to previous month

Last Year

0%

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

3

electron-winstaller app-builder-lib builder-util

Dev Dependencies

2

@types/archiver @types/fs-extra

electron-builder

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. 📦

Always looking for community contributions! 👀 Setting up a dev environment is easy to do 🪩

Sponsors

Notes, Tasks, Projects. All in a Single Place.
Your gateway to understanding your diabetes data	An open, source-available software licensing and distribution API
ToDesktop: An all-in-one platform for building and releasing Electron apps	Dashcam: Capture the steps to reproduce any bug with video crash reports for Electron.

Documentation

See the full documentation on electron.build.

NPM packages management:
- Native application dependencies compilation (including Yarn support).
- Development dependencies are never included. You don't need to ignore them explicitly.
- Two package.json structure is supported, but you are not forced to use it even if you have native production dependencies.
Code Signing on a CI server or development machine.
Auto Update ready application packaging.
Numerous target formats:
- All platforms: 7z, zip, tar.xz, tar.7z, tar.lz, tar.gz, tar.bz2, dir (unpacked directory).
- macOS: dmg, pkg, mas.
- Linux: AppImage, snap, debian package (deb), rpm, freebsd, pacman, p5p, apk.
- Windows: nsis (Installer), nsis-web (Web installer), portable (portable app without installation), AppX (Windows Store), MSI, Squirrel.Windows.
Publishing artifacts to GitHub Releases, Amazon S3, DigitalOcean Spaces and Bintray.
Advanced building:
- Pack in a distributable format already packaged app.
- Separate build steps.
- Build and publish in parallel, using hard links on CI server to reduce IO and disk space usage.
- electron-compile support (compile for release-time on the fly on build).
Docker images to build Electron app for Linux or Windows on any platform.
Proton Native support.
Downloads all required tools files on demand automatically (e.g. to code sign windows application, to make AppX), no need to setup.

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

Installation

Yarn is strongly recommended instead of npm.

yarn add electron-builder --dev

Note for Yarn 3

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.

Quick Setup Guide

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:
```
1"build": {
2  "appId": "your.id",
3  "mac": {
4    "category": "your.app.category.type"
5  }
6}
```
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:
```
1"scripts": {
2  "app:dir": "electron-builder --dir",
3  "app:dist": "electron-builder"
4}
```
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.

Programmatic Usage

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.

1"use strict"
2
3const builder = require("electron-builder")
4const Platform = builder.Platform
5
6// Promise is returned
7builder.build({
8  targets: Platform.MAC.createTarget(),
9  config: {
10   "//": "build options, see https://goo.gl/QQXmcV"
11  }
12})
13  .then(() => {
14    // handle result
15  })
16  .catch((error) => {
17    // handle error
18  })

Boilerplates

electron-webpack-quick-start — A bare minimum project structure to get started developing with electron-webpack. Recommended.
electron-react-boilerplate A boilerplate for scalable cross-platform desktop apps.
electron-react-redux-boilerplate A minimal boilerplate to get started with Electron, React and Redux.
electron-boilerplate A minimalistic yet comprehensive boilerplate application.
Vue CLI 3 plugin for Electron A Vue CLI 3 plugin for Electron with no required configuration.
electron-vue-vite A real simple Electron + Vue3 + Vite5 boilerplate.
vite-electron-builder Secure boilerplate for Electron app based on Vite. Supports multiple frameworks.
electronjs-with-nextjs ElectronJS application with NextJS and TypeScript.

Debug

Set the DEBUG environment variable to debug what electron-builder is doing:

1DEBUG=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. bash set DEBUG=electron-builder

!!! tip "PowerShell" PowerShell uses different syntax to set environment variables. bash $env:DEBUG=electron-builder

Donate

We do this open source work in our free time. If you'd like us to invest more time on it, please donate.

Empty State

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

9

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

8

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

6

SAST

Determines if the project uses static code analysis.

3

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 3

Details

Warn: containerImage not pinned by hash: docker/base/Dockerfile:3: pin your Docker image by updating buildpack-deps:22.04-curl to buildpack-deps:22.04-curl@sha256:00d9d5d1f0f0e615ec87d1d09625f7ca94960a94f472005b5ca0550b741276e9
Warn: containerImage not pinned by hash: docker/node/Dockerfile:2
Warn: containerImage not pinned by hash: docker/wine-chrome/Dockerfile:2
Warn: containerImage not pinned by hash: docker/wine-mono/Dockerfile:2
Warn: containerImage not pinned by hash: docker/wine/Dockerfile:2
Warn: containerImage not pinned by hash: mkdocs-dockerfile:1: pin your Docker image by updating squidfunk/mkdocs-material:9.5 to squidfunk/mkdocs-material:9.5@sha256:41942f7a2f5163aacd0e866e076d95db4f26550b97d76c1594c04250cbb580e9
Warn: containerImage not pinned by hash: test/src/updater/Dockerfile-appimage:1: pin your Docker image by updating buildpack-deps:noble-curl to buildpack-deps:noble-curl@sha256:8e7e0c787a677d90917f6cacd7d108f3a3022e51d6bff9b46dc8bf5802b368b2
Warn: containerImage not pinned by hash: test/src/updater/Dockerfile-archlinux:1: pin your Docker image by updating archlinux:latest to archlinux:latest@sha256:7ca06cad29fe509ea1b4a0fb40485ca410fe5fdbea39888c5f3169b4961b2b14
Warn: containerImage not pinned by hash: test/src/updater/Dockerfile-debian:1: pin your Docker image by updating debian:bookworm-slim to debian:bookworm-slim@sha256:6ac2c08566499cc2415926653cf2ed7c3aedac445675a013cc09469c9e118fdd
Warn: containerImage not pinned by hash: test/src/updater/Dockerfile-rpm:1: pin your Docker image by updating fedora:latest to fedora:latest@sha256:6beec36f3b1c7fd128bb69a59e20d4a897e65a43145ebb252fb39923c98c1c8b
Warn: downloadThenRun not pinned by hash: docker/base/Dockerfile:8-22
Warn: npmCommand not pinned by hash: docker/node/Dockerfile:11
Warn: pipCommand not pinned by hash: mkdocs-dockerfile:2
Warn: downloadThenRun not pinned by hash: test/src/updater/Dockerfile-appimage:46
Warn: npmCommand not pinned by hash: test/src/updater/Dockerfile-appimage:48
Warn: npmCommand not pinned by hash: test/src/updater/Dockerfile-archlinux:13
Warn: downloadThenRun not pinned by hash: test/src/updater/Dockerfile-debian:5
Warn: npmCommand not pinned by hash: test/src/updater/Dockerfile-debian:8
Warn: npmCommand not pinned by hash: test/src/updater/Dockerfile-rpm:23
Info: 15 out of 15 GitHub-owned GitHubAction dependencies pinned
Info: 9 out of 9 third-party GitHubAction dependencies pinned
Info: 0 out of 1 pipCommand dependencies pinned
Info: 0 out of 10 containerImage dependencies pinned
Info: 0 out of 3 downloadThenRun dependencies pinned
Info: 0 out of 5 npmCommand dependencies pinned

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

5.7

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.