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

measure-perf

v0.1.1

Published

Measure the execution time of a script in JS

Readme

Measure Perf

Installation

This module is distributed via [npm][npm] which is bundled with [node][node] and should be installed as one of your project's dependencies:

with napm:

npm install --save measure-perf

or with yarn

yarn add measure-perf

Usage

Module exports 4 functions:

start

function(name: string, log?: () => void): () => void

Starts the measurement of [name]

First argument is a measurement name - should be unique for each measurement, second is an optional log function. If log function is supplied, it gets run along with starting the measurement.

It returns a finishing function: function(): void. You should use this end function instead of an imported one, if your code is asynchronous, to properly pair the measurements. If you use a standalone end() function, it will end the last started measurement with the given name

end

function(name: string, id?: number, log?: () => void): void

Ends the measurement of [name]

First argument is a measurement name - the one you want to finish. Second argument is an id of the started measurmenet. If you are always ending the most last measurement, there's no need to supply the id. If not, there's no good way of getting the id right now. You should use the returned function from start().

exportMeasurementsOf

function(name: string)

Returns all the measurements of [name] with computed statistic

Measurement Statistics:

{
  values:    Measurement[]         // measurements with added statistics
  mean:     number                // average of value durations
  min:      number                // minimal duration of values
  max:      number                // maximal duration of values
  pending:  number                // number of started, but not ended measurements
}

Measurement:

{
  start:              number      // starting time
  end:                number      // end time
  duration:           number      // difference between end and start times
  standardDeviation:  number      // standard deviation of duration
  fromPrev:           number      // difference to previous duration (positive means longer; negative means shorter)
}

exportMeasurements

All the measurements grouped by name