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

lab-assistant

v0.2.0

Published

A Puppeteer-based tool that does the grunt work of taking measurements and figuring out how much of a performance change there is between two different versions of your site.

Readme

lab-assistant

lab-assistant is a Puppeteer-based tool that does the grunt work of taking measurements and figuring out how much of a performance change there is between two different versions of your site.

This is a useful tool to run every time you're working on a loading performance improvement. It will help you gauge whether the improvement is real and not just placebo, and it'll give you a number to attach to your PR description, blog post, or annual employee self-assessment survey.

Impress your peers with actual numbers!

Usage

The easiest way to use lab-assistant is with a tool like npx:

npx lab-assistant http://v1.mysite.tld http://v2.mysite.tld

Here's the current full set of options (which you can get with --help):

lab-assistant.js <url> [url2]

Positionals:
  url   URL to fetch content from.
        If `url2` is not specified, this is used for both the new and old
        versions, with the application pausing in between to allow for the
        version swap.
  url2  Second URL to fetch content from.
        If specified, this refers to the new version, while `url` refers to
        the old version.

Options:
      --help          Show help                                        [boolean]
  -v, --verbose       Output more details.            [boolean] [default: false]
      --headless      Whether to use a headless browser.
                                                       [boolean] [default: true]
  -l, --lighthouse    Whether to run the tests through Lighthouse.
                      Measuring through Lighthouse is significantly slower, and
                      the results aren't comparable to direct measuring.
                                                      [boolean] [default: false]
  -r, --repeat        The number of measurements to take for each version.
                                                          [number] [default: 10]
  -t, --throwaway     The number of throwaway visits to perform before any
                      actual measurements.
                      Keeping it at 1 or increasing the value can help with
                      stability.                           [number] [default: 1]
  -c, --cpu_slowdown  The CPU slowdown throttling to apply (may help achieve
                      more stable results in CPU-heavy pages).          [number]
  -m, --metric        The metric to consider.
                      Metrics:
                      - ttfb: Time to First Byte
                      - fp: First Paint
                      - fcp: First Contentful Paint
                      - dcl: Time to DOMContentLoad event end
                      - load: Time to Load event end
                      - lcp: Largest Contentful Paint
                      - cls: Cumulative Layout Shift
                      - tti: Time To Interactive (Lighthouse only)
                      - tbt: Total Blocking Time (Lighthouse only)
     [string] [choices: "ttfb", "fp", "fcp", "dcl", "load", "lcp", "cls", "tti",
                                                        "tbt"] [default: "load"]

License

lab-assistant is licensed under GNU General Public License v2 (or later).