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

github-update-checker

v1.2.0

Published

Compares project's package.json version and latest GitHub tag version. `uptodate` method returns true (up to date) or false (needs update).

Downloads

6

Readme

#github-update-checker

Compares project's package.json version and latest GitHub tag version and returns the result.

It's really dumb, it just extracts all numbers from a tag name and doesn't use semver, so "v1.1.1" will become "111".

github-update-checker automatically tries to get project's package.json and construct a URL to GitHub API from repository.url section, but can get everything as an option.

##Methods

###uptodate

uptodate takes callback or options as an argument.

####Callback:

uptodate( callback(answer) )

answer

Type: Boolean or String

true (up to date), false (needs update) or 'error'.

####Options:

uptodate({
    packagePath: '/www/myproject/package.json',
    url        : 'https://api.github.com/repos/LOGIN/PROJECT/tags',
    timeout    : 10000
    callback   : callback
})

packagePath

Type: String

Absolute path to project's package.json file. github-update-checker will try to find it itself.

url

Type: String

Full URL to project's GitHub tags API. github-update-checker will try to construct it automatically from repository.url in package.json.

timeout

Type: Number

When give up waiting for GitHub API response. Default is 3000ms.

callback

Type: Function

Gets true (up to date), false (needs update) or 'error'.

Example

var updater = require( 'github-update-checker' );

updater.uptodate(function( uptodate ) {
    // uptodate is true, false or 'error'
});

Bitdeli Badge