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

relative-microtime

v2.0.0

Published

Get the number of microseconds elapsed since January 1, 1970 00:00:00 UTC without fear of clock drift

Downloads

1,310,404

Readme

relative-microtime

This module returns the number of microseconds elapsed since January 1, 1970 00:00:00 UTC.

Note: The returned number of microseconds are locked relative to a specific time and is therefore not subject to clock drift. This is contrary to how Date.now() operates, whos return value (in milliseconds) is always based on the system clock.

npm build status js-standard-style

Installation

npm install relative-microtime --save

Usage

const timer = require('relative-microtime')()

const milli = Date.now()
const micro = timer()

console.log(milli) // 1537446194859
console.log(micro) // 1537446194859132

Gotcha

API

timer = microtime()

Sync the microtime clock to the UTC wall clock.

Returns a timer function synced with the UTC time when microtime() was called. Any clock drift that happens after the call to microtime() will not influence the returned timer.

timer()

Returns a Number representing the microseconds elapsed since the UNIX epoch.

License

MIT