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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@crazyvinc/updater

v1.0.0

Published

The update system from @CrazyVinc/LED-Controller

Readme

AutoUpdater

This update system is used in @CrazyVinc/Led-Controller

Features

  • Get remote version from JSON
  • Download the update.
  • Extractor with the function to specify what to extract
  • Run npm install with the default extractor
  • Automatically download the correct extractor.
  • Define your own extractor

Example to run the default updater and run npm install

autoupdater -dest=./ -zip=./temp/update.zip -extractfile=installer.json -npm

To use the built-in extractor, You can define what to extract:

{
   "extract": {
       "files": [
           "/index.js",
           "/installer.json",
           "/package.json"
       ],
       "directories": [
           "/src"
       ]
   }
}

Recommend use:

  1. Use a launcher to run your main program.
  2. Let your program scan for updates in the background.
  3. If a update is found, install the update and the extractor.
  4. Let your main program communicate to your launcher that there is a update ready to install.
    • Send a JSON object with the path to the update and the path to the extractor
    • Send a prepared commandline string.
  5. Let the launcher stop your program and start the update-extractor (with child process spawn).
  6. Start your main program as soon the update-extractor is closed.

You can use the @CrazyVinc/Led-Controller Launcher and change it according to your own use