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 🙏

© 2026 – Pkg Stats / Ryan Hefner

aerate

v1.1.0

Published

Measure frontend performance against a budget using lovely charts in a browser

Readme

Four Kitchens

Aerate Logo

Measure frontend performance against a budget with an optional UI

Usage

  1. Get a WebPageTest.org API key
  2. yarn add aerate or npm i aerate
  3. Require Aerate in your project:
const aerate = require('aerate');
  1. Call the function with the options (options below):
aerate({
  key: 'YOUR_API_KEY',
  tests: [
    {
      name: 'Four Kitchens',
      url: 'http://fourkitchens.com/', // Or use relative urls for local tests
      type: 'homepage'
    }
  ]
});
  1. For a shorter command, add a script to your package.json
"scripts": {
  "aerate": "node aerate.js" (or whatever file you're using locally)
}
  1. npm run aerate or yarn aerate
  2. (Optional) Create/copy your own budget.json file using the following format:
{
  "TTFB": { // WPT Statistic name
    "name": "First Byte", // Readable Name presented on UI
    "description": "Time to First Byte is measured as the time from the start of the initial navigation until the first byte of the base page is received by the browser (after following redirects).",
    "value": "300" // Budgeted Value
  }
}

See /docs/stats.md for the list of available budget statistics

Available Options:

  1. key: REQUIRED API Key
  2. tests: REQUIRED tests to run
  3. connection: OPTIONAL defaults to 'Mobile LTE'
  4. count: OPTIONAL how many tests to run (WebPageTest.org supports up to 9)
  5. ui: OPTIONAL open Aerate UI in browser vs. console (defaults to false)
  6. localPort: OPTIONAL for local testing, enter your environment port

How do I set up the dev environment?

  1. clone repo, cd into it and run yarn to install dependencies
  2. Run gulp (opens up the UI with fake data populated from mapper/fake-results.json)

PostCSS usage: If you would like any new PostCSS plugins installed, the steps are as follows:

  1. npm install --save-dev PLUGIN_NAME
  2. Add your plugin to gulpfile.js at the top like the others and reference that addition in the postCSS call