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

chronograph

v0.0.0

Published

A wrapper for console.time with unique labels

Downloads

1

Readme

Chronograph

This is a tiny wrapper around console.time that adds a random identifier to your label.

Why do you want this? You want this because a Node.js process will handle many HTTP requests at once, and calls to console.time('foo') and console.endTime('foo') are not isolated on a per-request basis. As an example:

  • Alice makes a request to '/'
  • Your app calls console.time('root')
  • Some asynchronous things happen to serve Alice's request.
  • Bob makes a request to '/'
  • Your app makes another call to console.time('root')
  • The asynchronous things from Alice's request are done and callbacks are called.
  • Your app calls console.endTime('root')

You wanted to time how long it took to serve Alice's request. What you got instead was some irrelevant duration between the beginning of Bob's request and the end of Alice's.

This library attempts to solve that problem by keeping a randomly generated id for every call to console.time and console.timeEnd.

Use it like this:

Chronograph = require('chronograph');

chronograph = new Chronograph('my great label');
// 153ms later...
chronograph.end();
// logged: "my great label (gzosz8vx2f) 153ms"