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

greenkeeper-postpublish

v2.0.0

Published

postpublish hook for announcing new versions to greenkeeper

Downloads

40

Readme

greenkeeper-postpublish

Greenkeeper badge

Set up greenkeeper-postpublish

To install greenkeeper-postpublish save it to your devDependencies:

npm install greenkeeper-postpublish --save-dev

Then add it to your scripts in your package.json:

  "scripts": {
    "postpublish": "greenkeeper-postpublish --secret=$GK_NPMHOOK_SECRET --installation=$GK_INSTALLATION_ID"
  }

You can also set the secret and installation values in your publish environment:

gk_secret=$GK_NPMHOOK_SECRET
gh_installation=$GK_INSTALLATION_ID

Where the GK_NPMHOOK_SECRET is set in your Greenkeeper Enterprise Admin Dashboard at https://gke.your-company.com:8800 and GK_INSTALLATION_ID can be found in your GitHub Enterprise setup on the organisation for your modules: https://ghe.your-company.com/organizations/$organisation_name/settings/installations -> Greenkeeper -> the integer number in the URL.

When set up like this, every time your release the package (with npm publish), it will let Greenkeeper know that there is a new version available.

Manual use

You can also run it outside of the package.json scripts. You will need to install it with the --global flag then though:

npm install greenkeeper-postpublish --global

If you run greenkeeper-postpublish in a directory with a package.json it will parse it and use its name and version.

You can also specify the --pkgname and --pkgversion parameters instead:

greenkeeper-postpublish --pkgname mypackage --pkgversion 4.2.0 --secret=abcd --installation=54321

🌴