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

@springworks/high-resolution-millisecond-timer

v3005.77.0

Published

A small util to create timers that can measure sub-millisecond time in a consistently accurate way.

Downloads

264

Readme

@springworks/high-resolution-millisecond-timer

A small util to create timers that can measure sub-millisecond time in a consistently accurate way.

yarn add @springworks/high-resolution-millisecond-timer

Usage

import { createHighResolutionMillisecondTimer } from '@springworks/high-resolution-millisecond-timer';

// Create a timer
const timer = createHighResolutionMillisecondTimer();

// Run the code that you want to measure.
someFunction();

// Save the elapsed time in a variable.
// This is the number of milliseconds that `someFunction` took to run but in nanosecond resolution.
const elapsed_time = timer();

console.log(`someFunction took ${elapsed_time} ms to run.`);
// This will log something like "someFunction took 3.214684 ms to run."

// Even invoking the function immediately will result in a tangible measurement.
createHighResolutionMillisecondTimer()(); // <- note the extra invocation.
// this will return something like 0.001802

Why use this instead of new Date() or Date.now()?

The Date API gets it's current time from the operating system and as such is subject to clock drift. This means that the OS can decide to change what time it is between your measurements. You can even end up going back in time...

This function uses the HR Timer API and does not depend on what the OS think the clock is right now.