Return to site

Electron Winstaller

broken image


Config NameDescription
appDirectoryThe authors value for the nuget package metadata. Defaults to the author field from your app's package.json file when unspecified.
ownersThe owners value for the nuget package metadata. Defaults to the authors field when unspecified.
exeThe name of your app's main .exe file. This uses the name field in your app's package.json file with an added .exe extension when unspecified.
descriptionThe description value for the nuget package metadata. Defaults to the description field from your app's package.json file when unspecified.
versionThe version value for the nuget package metadata. Defaults to the version field from your app's package.json file when unspecified.
titleThe title value for the nuget package metadata. Defaults to the productName field and then the name field from your app's package.json file when unspecified.
nameWindows Application Model ID (appId). Defaults to the name field in your app's package.json file.
certificateFileThe path to an Authenticode Code Signing Certificate
certificatePasswordThe password to decrypt the certificate given in certificateFile
signWithParamsParams to pass to signtool. Overrides certificateFile and certificatePassword.
iconUrlA URL to an ICO file to use as the application icon (displayed in Control Panel > Programs and Features). Defaults to the Atom icon.
setupIconThe ICO file to use as the icon for the generated Setup.exe
setupExeThe name to use for the generated Setup.exe file
setupMsiThe name to use for the generated Setup.msi file
noMsiShould Squirrel.Windows create an MSI installer?
remoteReleasesA URL to your existing updates. If given, these will be downloaded to create delta updates
remoteTokenAuthentication token for remote updates

Module to generate Windows installers for Electron apps - 4.0.1 - a TypeScript package on npm - Libraries.io.

NPM module that builds Windows installers for Electron apps using Squirrel. Need for speed most wanted installation code.

Electron Winstaller

Installing

Usage

Require the package:

Then do a build like so.

After running you will have an .nupkg, a RELEASES file, and a .exe installer file in the outputDirectory folder for each multi task target given under the config entry. Ministry of sound annual spring 2004.

  1. Windows installer: It provides an electron-winstaller that creates a windows installer to install your desktop application. Why Build Desktop Apps with React 'Learn once, write everywhere' 'Build once, compose everywhere' React Native's slogan is 'Learn once, write anywhere'.
  2. Tools, electron, deploy, windows, desktop One of the ways that an Electron app can be packaged for distribution is by using Electron Forge. For Windows, there are currently two options for the kind of installer that Electron Forge can make, WiX and Squirrel.Windows.
  3. For building Windows Installers for Electron apps, the most popular choice is the Squirrel-based electron-winstaller npm module. However, electron-winstaller does not allow custom parameters for the produced installer or executing elevated PowerShell; as a result, we chose to use WiX Toolset (specifically, we chose the npm module wixtoolset.

There are several configuration settings supported:

Config NameRequiredDescription
appDirectoryYesThe folder path of your Electron app
outputDirectoryNoThe folder path to create the .exe installer in. Defaults to the installer folder at the project root.
loadingGifNoThe local path to a .gif file to display during install.
authorsYesThe authors value for the nuget package metadata. Defaults to the author field from your app's package.json file when unspecified.
ownersNoThe owners value for the nuget package metadata. Defaults to the authors field when unspecified.
exeNoThe name of your app's main .exe file. This uses the name field in your app's package.json file with an added .exe extension when unspecified.
descriptionNoThe description value for the nuget package metadata. Defaults to the description field from your app's package.json file when unspecified.
versionNoThe version value for the nuget package metadata. Defaults to the version field from your app's package.json file when unspecified.
titleNoThe title value for the nuget package metadata. Defaults to the productName field and then the name field from your app's package.json file when unspecified.
certificateFileNoThe path to an Authenticode Code Signing Certificate
certificatePasswordNoThe password to decrypt the certificate given in certificateFile
signWithParamsNoParams to pass to signtool. Overrides certificateFile and certificatePassword.
iconUrlNoA URL to an ICO file to use as the application icon (displayed in Control Panel > Programs and Features). Defaults to the Atom icon.
setupIconNoThe ICO file to use as the icon for the generated Setup.exe
setupExeNoThe name to use for the generated Setup.exe file
noMsiNoShould Squirrel.Windows create an MSI installer?
remoteReleasesNoA URL to your existing updates. If given, these will be downloaded to create delta updates
remoteTokenNoAuthentication token for remote updates

Sign your installer or else bad things will happen

Electron-winstaller Npm

For development / internal use, creating installers without a signature is okay, but for a production app you need to sign your application. Internet Explorer's SmartScreen filter will block your app from being downloaded, and many anti-virus vendors will consider your app as malware unless you obtain a valid cert.

Any certificate valid for 'Authenticode Code Signing' will work here, but if you get the right kind of code certificate, you can also opt-in to Windows Error Reporting. This MSDN page has the latest links on where to get a WER-compatible certificate. The 'Standard Code Signing' certificate is sufficient for this purpose.

Handling Squirrel Events

Squirrel will spawn your app with command line flags on first run, updates, and uninstalls. it is very important that your app handle these events as early as possible, and quit immediately after handling them. Squirrel will give your app a short amount of time (~15sec) to apply these operations and quit.

The electron-squirrel-startup module will handle the most common events for you, such as managing desktop shortcuts. Just add the following to the top of your main.js and you're good to go:

You should handle these events in your app's main entry point with something such as:

Debugging this package

Electron App Tutorial

You can get debug messages from this package by running with the environment variable DEBUG=electron-windows-installer:main e.g.

Current Tags

  • 4.0.0 .. latest (4 years ago)

Electron Installer

50 Versions

Electronic Installer

  • 4.0.0 .. 4 years ago
  • 3.1.0 .. 4 years ago
  • 3.0.0 .. 4 years ago
  • 2.11.7 .. 4 years ago
  • 2.11.6 .. 4 years ago
  • 2.11.5 .. 4 years ago
  • 2.11.4 .. 4 years ago
  • 2.11.3 .. 4 years ago
  • 2.11.1 .. 4 years ago
  • 2.11.0 .. 4 years ago
  • 2.10.2 .. 4 years ago
  • 2.10.1 .. 4 years ago
  • 2.10.0 .. 4 years ago
  • 2.9.6 .. 5 years ago
  • 2.9.5 .. 5 years ago
  • 2.9.4 .. 5 years ago
  • 2.9.3 .. 5 years ago
  • 2.9.2 .. 5 years ago
  • 2.9.1 .. 5 years ago
  • 2.9.0 .. 5 years ago
  • 2.8.3 .. 5 years ago
  • 2.8.2 .. 5 years ago
  • 2.8.1 .. 5 years ago
  • 2.8.0 .. 5 years ago
  • 2.7.1 .. 5 years ago
  • 2.7.0 .. 5 years ago
  • 2.6.2 .. 5 years ago
  • 2.6.1 .. 5 years ago
  • 2.6.0 .. 5 years ago
  • 2.5.0 .. 5 years ago
  • 2.4.0-beta.1 .. 5 years ago
  • 2.4.0-beta.0 .. 5 years ago
  • 2.3.0-beta.4 .. 5 years ago
  • 2.3.0-beta.3 .. 5 years ago
  • 2.3.0-beta.2 .. 5 years ago
  • 2.3.0-beta.1 .. 5 years ago
  • 2.3.0-beta.0 .. 5 years ago
  • 2.2.1-beta.0 .. 5 years ago
  • 2.0.6-beta.8 .. 5 years ago
  • 2.0.6-beta.7 .. 5 years ago
  • 2.0.6-beta.6 .. 5 years ago
  • 2.0.6-beta.5 .. 5 years ago
  • 2.0.6-beta.4 .. 5 years ago
  • 2.0.6-beta.3 .. 5 years ago
  • 2.0.6-beta.2 .. 5 years ago
  • 2.0.6-beta.1 .. 5 years ago
  • 2.0.6-beta.0 .. 5 years ago
  • 2.0.5-beta.7 .. 5 years ago
  • 2.0.5-beta.5 .. 5 years ago
  • 2.0.5-beta.4 .. 5 years ago




broken image