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 🙏

© 2024 – Pkg Stats / Ryan Hefner

electron-installer

v1.0.3

Published

Cross-platform CLI tool for installing Electron distributions

Downloads

17

Readme

electron-installer · tests status typescript license badge npm version

electron-installer is a command-line utility written in Node.js that streamlines the process of preparing an Electron distribution.

This utility is intended for use in automated build pipelines or for development and testing purposes.

  • Supports all platforms, architectures and versions.
  • Caches builds to avoid unnecessary downloads.
  • Minimal external dependencies: JSZip.

Installation

npm install electron-installer -g

Usage

Usage: electron-installer [options]

Options:
  --help                Show this help message and exit.
  --target-dir          Specify a target directory to install to.
  --version             Specify a version to install (e.g 23.0.0)
  --no-cache            Disable caching of downloaded builds.
  --clear-cache         Clears the cache of downloaded builds.
  --platform <string>   Override the platform to install for.
  --arch <string>       Override the architecture to install for.
  --exclude <pattern>   Exclude files matching the given pattern.
  --locale <a,b,c..>    Define which locales to include in the build (defaults: all).

Documentation

Verions

Using the --version <version> option you can specify a specific version of Electron to install. This should be a valid version number such as 23.0.0 or 24.0.0-alpha.1.

electron-installer --version 24.0.0-alpha.1

If no version is specified, the latest stable version will be installed. This is determined by querying the directory listing of the download server.

electron-installer # No version, latest is installed.

Target Directory

By default, Electron will be installed in the current working directory. To specify your own target directory, use the --target-dir option.

electron-installer --target-dir /path/to/target # Installs to /path/to/target.

Keep in mind that files will be overwritten if they already exist in the target directory.

The --target-directory option also supports some substitution variables that can be used to dynamically generate the target directory.

| Variable | Description | Example | | -------- | ----------- | ------- | | {version} | The version of Electron being installed. | 23.0.0 | | {platform} | The platform being installed for. | win32 | | {arch} | The architecture being installed for. | x64 | | {package} | The name of the package being installed. | electron-v24.0.0-alpha.1-win32-arm64 |

electron-installer --target-dir="/{package}" # Installs to /electron-v23.0.0-win32-x64
electron-installer --target-dir="/{version}/{platform}" # Installs to /23.0.0/win32

Platform / Architecture

By default, the platform and architecture of the current system will be used. If you wish to override this, use the --platform and --arch options.

electron-installer --platform win32 --arch x64 # Installs latest stable build for Windows x64.

At the time of writing, the following platforms and architectures are supported: | Platform | Architecture | | -------- | ------------- | | win32 | x64, ia32, arm64 | | linux | x64, arm64, armv7l | | darwin | x64, arm64 | | mas | x64, arm64 |

This utility does not validate against this table, and will attempt to download the build regardless of the platform or architecture specified. If the build does not exist, the download will fail.

Caching

By default, downloaded builds are cached to the operating system's temporary directory. Installing the same version multiple times will re-use the cached build, avoiding unnecessary downloads.

Path: os.tmpdir() + '/electron-installer-cache/' + package

To disable this behavior, use the --no-cache option. The cache will not be checked or updated when this option is used.

electron-installer --no-cache # Disables caching.

Additionally, the --clear-cache option can be used to clear the cache before a build starts. The cache will still be used unless --no-cache is also set.

electron-installer --clear-cache # Clears the cache before installing.

Excluding Files

Providing the --exclude <pattern> option allows you to exclude files that match the pattern from the build. The pattern should be a valid regular expression.

electron-installer --exclude "^ffmpeg.dll$" # Excludes ffmpeg.dll from the build.

Notes on file exclusion:

  • The pattern is matched against the file path as it appears inside the ZIP archive, not the final file path on disk.
  • To exclude locale files more efficiently, see the Locales section.

Locale

By default, builds come with locale files for all languages supported by Chromium. According to the developer of nw.js, it is safe to remove locale files that you won't be using.

electron-installer makes this simple with the --locale <locales> option, where <locales> is a comma-separated list of locales to include.

You can find a list of locales supported by Chromium here.

electron-installer --locale "sw,en-GB,en_US"

Notes on locale:

  • You should use the locale IDs that Chromium uses, not platform-specific variations. For example, don't use en (OSX variation) for en-US, electron-installer will automatically adjust this when installing for OSX.
  • The locale files are not related to the language content of your application, it is related to the environment in which the application will be deployed. Do not exclude locale files unless you are 100% sure of the locale of the computers your application will be deployed onto.
  • The use of hyphens and underscores differs between platforms, as such you can use either and electron-installer will automatically adjust them depending on the target platform (e.g en-gb == en_gb).
  • Locale flags are case-insensitive (e.g en-GB == en-gb).

Contributing / Feedback / Issues

Feedback, bug reports and contributions are welcome. Please use the GitHub issue tracker and follow the guidelines found in the CONTRIBUTING file.

License

The code in this repository is licensed under the ISC license. See the LICENSE file for more information.