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

tiny-timestamp

v1.0.0

Published

Create a tiny representation of the timestamp

Downloads

205

Readme

TinyTimstamp

Unique small timestamps.

Handy for cross referencing logs or error reports, especially if your users tend to send you screenshots and you don't want to be transcribing long codes.

It encodes a timestamp based on process.hrtime() to create unique identifiers. See below for how this is handled

npm install tiny-timestamp
const { decodeStamp, tinyStamp, toISOString } = require('tiny-timestamp');

const value = tinyStamp();
const originalTime = decodeStamp(value);

console.log(value); // '2tLJTc:s9V'
console.log(originalTime); // [ 1606876750, 123451 ]
console.log(toISOString(value)); // '2020-12-02T02:39:10.000123451'

// You can shorten identifiers by setting a repeat interval
// and any precision above that period will be discarded

const month = 60 * 60 * 24 * 30; // in seconds
const shorterValue = tinyStamp({
	repeatableInterval: month,
	time: originalTime,
});
console.log(shorterValue); // -eXc:s9V

// You won't be able to get back the exact original time
console.log(decodeStamp(shorterValue)); // [ 2428750, 123451 ]
console.log(toISOString(shorterValue)); // '1970-01-29T02:39:10.000123451'

Under the hood

hrtime() produces a time in nanoseconds, though it's not guaranteed to have nanosecond precision, the precision should be good enough to give a low likelihood of collision between two identifiers.

However, because hrtime() is calculated in seconds from some arbitrary time, on it's own it can't produce a good unique identifier. tinyStamp replaces the seconds value from hrtime with the seconds since the UNIX epoch.

In other words

const arbitraryTime = process.hrtime();
const fixedTime = [parseInt(new Date() / 1000), arbitraryTime[1]];