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

howlongdidittake

v0.1.0

Published

Measure elapsed time. Format with s, ms or ns. Both CLI and API. Small bundling size.

Downloads

3

Readme

HowLongDidItTake

Measure elapsed time.

  • Simple. Lightweight. TypeScript friendly. Small bundling size.
  • Format the result. Choose s, ms or ns. Even automatically.
  • Limit the precision or the fraction digits.
  • Available on both Node.js and browsers (maybe).

CLI

Use hldit command.

hldit (any command)
hldit (any *.js filepath)
  • On CLI, the unit is determined automatically and the precision is always 2. I.e. just like autoUnit(2) via the API (see below).
  • If a given JavaScript file has a default export of any Promise type, hldit awaits until the Promise is resolved.

API

Import

import * as hldit from "howlongdidittake";

Stopwatch

const getElapsedTime = hldit.stopwatch.autoUnit(2); // give precision
console.log(getElapsedTime());
const getElapsedTime = hldit.stopwatch.withUnit("ms", 2); // give unit and fraction digits
console.log(getElapsedTime());

Measure

const anyAsyncCallback = () => Promise.resolve();

const measure = hldit.measure.autoUnit(2); // give precision
measure(anyAsyncCallback).then((elapsedTime) => console.log(elapsedTime));
const anyAsyncCallback = () => Promise.resolve();

const measure = hldit.measure.withUnit("ms", 2); // give unit ant fraction digits
measure(anyAsyncCallback).then((elapsedTime) => console.log(elapsedTime));

hldit.measure has functions for sync callbacks as well.