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

hyperupdate

v1.2.2

Published

P2P Electron updater with binary diffing built in

Downloads

13

Readme

hyperupdate

P2P Electron updater with binary diffing built in

npm install hyperupdate

Status

Note that this project is still experimental

Usage

First setup the releaser in your app

npm install -g hyperupdate
cd your-electron-app
hyperupdate-release # will print a release config map

The release lines are store in ./hyperupdate, you might want to add this folder to your .gitignore.

Then in your Electron app, setup the updater in either your electron process or in the renderer process if you have Node.js integration enabled.

const Hyperupdate = require('hyperupdate')

const u = new Hyperupdate({
  darwin: '<from-above>',
  linux: '<from-above>',
  win32: '<from-above>'
})

u.on('update-available', () => {
  console.log('New update available', this.latestRelease)
})

u.on('update-downloaded', () => {
  console.log('New update downloaded', this.latestRelease)
})

After the update-downloaded event has fired you can use the updateAndRelaunch method to apply the new update

u.updateAndRelaunch() // will apply the update and relaunch your app

RPC

If you want to run the updater in the Electron process instead of the renderer you can use the RPC interface to access it.

In the Electron process do

await u.listen()

And then in renderer do

const Client = require('hyperupdate/client')

const u = new Client()

The remote client has the same interface as the normal updater instance.

Adding a new release

To add a new release, bump the version in your Electron's package.json and build your app using electron-builder.

Then point hyperupdate-release to the .app file on mac or unpacked directory on linux / windows.

# on mac
hyperupdate-release ./dist/mac/my-app.app

# on linux
hyperupdate-release ./dist/linux-unpacked

# on windows
hyperupdate-release ./dist/win-unpacked

Hyperupdate will chunk each release using a bundled rabin chunker, to try to make the update diff as small as possible.

After it has been added the updater will start swarming the new release.

If you the release you add is the same as the latest release, hyperupdate will just start swarming the releases instead of re-adding it.

License

MIT