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-updater-example-test

v0.8.17

Published

electron-updater example project

Downloads

3

Readme

This repo contains the bare minimum code to have an auto-updating Electron app using electron-updater with releases stored on GitHub.

If you can't use GitHub, you can use other providers:

NOTE: If you want to run through this whole process, either fork this repo or start your own from a template. Then replace all instances of iffy with your GitHub username before doing the following steps.

  1. For macOS, you will need a code-signing certificate.

    Install Xcode (from the App Store), then follow these instructions to make sure you have a "Developer ID Application" certificate. If you'd like to export the certificate (for automated building, for instance) you can. You would then follow these instructions.

    This example application is set up to perform code-signing and notarization on Mac OS provided that a Developer ID Application certificate is installed in the default keychain. The following environment variables are important for the signing process:

    • CSC_IDENTITY_AUTO_DISCOVERY - controls whether electron-builder tries to sign the application; default is true, set to false to skip signing
    • APPLE_ID - the Apple ID to use for notarization (required for signing).
    • APPLE_ID_PASSWORD - the password to use with the specified Apple ID for notarization (required for signing). Apple recommends setting up an app-specific password to safeguard the Apple ID password (see Apple Support) for more information.

    To enable code-signing and notarization:

     export CSC_IDENTITY_AUTO_DISCOVERY="true"
     export APPLE_ID="<your Apple ID>"
     export APPLE_ID_PASSWORD="<your Apple Password>"
  2. Adjust package.json if needed.

    By default, electron-updater will try to detect the GitHub settings (such as the repo name and owner) from reading the .git/config or from reading other attributes within package.json. If the auto-detected settings are not what you want, configure the publish property as follows:

     {
         ...
         "build": {
             "publish": [{
                 "provider": "github",
                 "owner": "iffy",
                 "repo": "electron-updater-example"
             }],
             ...
         }
     }
  3. Install necessary dependencies with:

     yarn

    or

     npm install
  4. Generate a GitHub access token by going to https://github.com/settings/tokens/new. The access token should have the repo scope/permission. Once you have the token, assign it to an environment variable

    On macOS/linux:

     export GH_TOKEN="<YOUR_TOKEN_HERE>"

    On Windows, run in powershell:

     [Environment]::SetEnvironmentVariable("GH_TOKEN","<YOUR_TOKEN_HERE>","User")

    Make sure to restart your IDE/Terminal to inherit latest env variable.

  5. Publish for your platform with:

     electron-builder -p always

    or

     npm run publish

    If you want to publish for more platforms, edit the publish script in package.json. For instance, to build for Windows and macOS:

     ...
     "scripts": {
         "publish": "electron-builder --mac --win -p always"
     },
     ...

    NOTE: The Mac OS signing/notarization process must be run on Mac OS.

  6. Release the release on GitHub by going to https://github.com/YOUR_GIT_HUB_USERNAME/electron-updater-example/releases, editing the release and clicking "Publish release."

  7. Download and install the app from https://github.com/YOUR_GIT_HUB_USERNAME/electron-updater-example/releases.

  8. Update the version in package.json, commit and push to GitHub.

  9. Do steps 5 and 6 again.

  10. Open the installed version of the app and see that it updates itself.