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

@jsenv/performance-impact

v4.4.9

Published

Report pull request impacts on performance metrics

Downloads

371

Readme

Performance impact npm package

@jsenv/performance-impact analyses a pull request impact on your performance metrics. This analysis is posted in a comment of the pull request on GitHub.

  • Helps you to catch big performance variations before merging a pull request
  • Gives you the ability to measure performances on your machine during dev
  • Can be added to any automated process (GitHub workflow, Jenkins, ...)

Disclaimer: This tool should not be used to catch small performance variations because they are hard to distinguish from the natural variations of performance metrics (see performance variability).

Pull request comment

Screenshot of a pull request comment

stuff

Performance variability

Performance metrics will change due to inherent variability, even if there hasn't been a code change. It can be mitigated by measuring performance multiple times. But you should always keep in mind this variability before drawing conclusions about a performance-impacting change.

With time you'll be capable to recognize unusual variation in your performance metrics.

How to catch small performance impacts?

Catching (very) small performance impacts with confidence requires repetition and time. You need to:

  1. Let your code be used a lot of times in a lot of scenarios and see the results. This could be scripts, real users or both.

  2. And or push your performance metrics in a tool like Kibana or DataDog and check the tendency of your performance metrics.

In any case it means you have to wait before knowing the real performance impact.

Recommended approach to catch performance impacts

  1. measure some performance metrics
  2. Big variations can be anticipated and catched by @jsenv/performance-impact
  3. For small variations, upload performance metrics to a dashboard. Then, periodically watch the dashboard to check performance metrics tendency over time