npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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




Deploy RiffRaff Artefacts




Node RiffRaff Artefact

Plugin for building deployable RiffRaff artefacts in Node. Supports RiffRaff deployment types:

  • cloud-formation
  • aws-lambda
  • autoscaling

Getting Started

This is a node plugin for creating RiffRaff artefacts that can then be deployed by RiffRaff. It builds the same package structure as the SBT equivalent.

To use it, ensure you have a package.json located in the root directory of your project. There must be at the very minimum the name field.

In your project root directory, type:

npm install node-riffraff-artefact --save

Options - these sit at the root level of your package.json

  • isAwsLambda: true or false (optional - defaults to false)
  • cloudformation: false or the location of your cloudformation (optional - defaults to cloudformation.json)
  • projectName: a string with the name you want to appear in RiffRaff dropdown (e.g. team::project - defaults to name in package.json)
  • cloudformationAppTag: a string with the value of the App tag for the cloudformation stack and the name of the cloudformation deployment in riff-raff.yaml (e.g. name-cloudformation - defaults to name in package.json with -cloudformation appended)
  • riffraffFile: path to a RiffRaff riff-raff.yaml for your app. Defaults to ./riff-raff.yaml.
  • uploadArtefact: true or false (optional - defaults to true). Determines if the artefact should be uploaded to S3.

Some example riff-raff.yaml:

AWS Lambda deploy with Cloudformation

    type: aws-lambda
      - name-from-package-json-
    type: cloud-formation
      templatePath: 'cloudformation/cloudformation.yaml'

Some example package.json:

Autoscaling deploy with Cloudformation

  "name": "s3watcher",
  "...": "...",
  "cloudformation": "my_cloudformation.json",
  "cloudformationAppTag": "s3watcher-cloudformation"

AWS Lambda deploy without Cloudformation

  "name": "s3watcher",
  "...": "...",
  "isAwsLambda": true,
  "cloudformation": false

You should also have a riff-raff.yaml in your root directory that can be read by RiffRaff, although the plugin will work without one.

Once you've set up the equivalent package.json, you will need to add an npm task riffraff-artefact. Running this will then generate the artefact for you and upload it to S3.

You may then wish to add build hooks into whatever continuous deployment you're using to deploy your artefact.

You can enable more verbose logging setting the environment variable VERBOSE=true.

Configuring the Default build directory

By default, this plugin will build the tgz file from the default directory (the root). You can configure this by setting buildDir to whatever you want in the package.json file. Note that this is the root directory that node will be run on. So a package.json with relevant run scripts must be present.

Build environment support

Works on:

  • Circle CI
  • Travis
  • Jenkins with the Git plugin
  • Teamcity. Note - you need to manually pass the branch name as an environment variable. Under Parameters, create an environment variable called TEAMCITY_BRANCH with the value<your build configuration ID>

If you want to support other continuous integration tools, have a look at settings.js and configure the relevant environment variables to get information about the build.


  • Clone
  • Update the code
  • npm build
  • Commit