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 🙏

© 2025 – Pkg Stats / Ryan Hefner

benchmark-me

v2.1.0

Published

A CLI tool to benchmark frontend developer tasks and compare machine performance.

Downloads

14

Readme

Frontend Developer Benchmark Suite

A command-line tool to run a series of realistic benchmarks that simulate the daily tasks of a frontend developer. This suite helps quantify performance differences between machines, providing concrete data to justify hardware upgrades.

The tool runs multiple tests, including dependency installation, build times, code linting, image processing, and other CPU/IO‑intensive tasks. It generates detailed JSON reports for each run, which can be used with the companion comparison UI.

Features

  • Realistic Scenarios: Tests are based on real‑world frontend development tasks.
  • Multiple Runs: Runs the entire test suite multiple times to ensure stable, reliable results.
  • Detailed Reports: Generates a separate JSON file for each run with timestamps, system info, and performance metrics.
  • Easy to Use: Interactive CLI for selecting tests and number of runs.

Installation

npm install -g benchmark-me

This makes the benchmark-me command available in your terminal.

How to Use

  1. Navigate to the root of a Next.js project you want to test.
  2. Run:
benchmark-me

Follow the prompts to select tests and the number of runs (default is 3). The script saves a benchmark-results-....json file for each run in your current directory.

The Tests

  • Clean Install: Cleans npm cache, deletes node_modules and .next, then runs npm install.
  • Clean Production Build: Deletes .next and runs npx next build.
  • TypeScript Type Check: Runs npx tsc --noEmit.
  • Linter: Runs npx next lint.
  • Image Processing: Programmatically generates and resizes 200 high‑resolution images using sharp.
  • File I/O: Creates and deletes 10,000 text files.
  • Heavy Node.js Script: Calculates a large number of prime numbers to stress the CPU.

Compare Results

After running the benchmarks on two different machines, use the companion web UI to upload the result files and visually compare performance.