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

cli-autoupdater

v1.1.0

Published

Auto-updating for node cli tools

Downloads

11

Readme

cli-autoupdater

Autoupdating library for node based cli tools

Some Possible Use Cases

Installation

# npm
npm install cli-autoupdater --save

# yarn
yarn add cli-autoupdater

Usage

autoupdater is called by passing in the "options" object and a Promise is returned. The result is a boolean value representing if an update was performed or not. So just wrap your application logic with the call to autoupdater!

autoupdater(require('./package.json');).then((updated) => {
  if (updated) {
    // The application was updated, so exit
    console.log('You may rerun the last command');
    process.exit();
  } else {
    // No update occurred, so just run the application
    run(); // Or whatever your application usually does here
  }
}).catch((e) => {
  // An error has occurred so
  console.log(e);
  process.exit()
});

You could pass in your own configuration object or just use your package.json file. The fields in use are:

{
  "name": "myApp",
  "version": "1.0.0",
  "autoupdater": {
    "updateMessage": "Would you like to update now?",
    "checkCommand": "npm show myApp version",
    "installCommand": "npm install -g myApp",
    "promptUser": true
  }
}

All autoupdater options are completely optional and usually the defaults are good enough.

The autoupdater simply looks at the version and compares it to the version in npm. If there is a newer version, the user is prompted to update. If promptUser is false, then the update is automatic.

License

cli-autoupdater is licensed under the MIT License.