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

please-update

v0.0.1

Published

Notify when you release a new version

Downloads

40

Readme

Notify when you release a new version

Example message

npm install please-update

Build Status Coverage Status

Why even?

Cool CLI tools will notify users when a new version releases so they can update. Please Update makes your CLI tool cool, fool.

Note: Programs that run longer than it takes for an HTTPS request can use this too.

Usage

import update from 'please-update'
import pkg from './package.json'

update({
  package: pkg.name,
  version: pkg.version
}).then(() => {
  /* message printed if an update is available */
})

Considerations

The is-ci library detects if a command runs on CI servers. If so, no message prints.

The default message will contain emoji when supported.

Documentation

Here are all the supported options.

| Property | Type | Default | Description | | -------- | ---- | ------- | ----------- | | package | string | required | The package name | version | string | required | The current, local package version | preferGlobal | boolean | false | Whether to show the global install command | includeTaggedVersions | boolean | false | Whether to count tagged versions (betas, alphas) as versions | persistCheck | boolean | true | Delegate to Please Update the task of remembering the last check time for an update | checkInterval | number | 24 hours | Number of milliseconds to wait before checking for an update again | lastCheck | number | 0 | The last check time in milliseconds. Needed if persistCheck is false. | displayFn | (info: object) -> void | built-in | Function passed all the data necessary to print an update warning. | preventUpdate | boolean | isCI | Whether to never check or display a warning | silenceErrors | boolean | true | Whether to ignore an error if the NPM registry is down

Contributing

Contributions are incredibly welcome as long as they are standardly applicable and pass the tests (or break bad ones). Tests are in AVA.

# running tests
npm run test

Follow me on Twitter for updates or for the lolz and please check out my other repositories if I have earned it. I thank you for reading.