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

unique-push-id

v1.0.2

Published

🆔 Generates unique, chronological, lexicographical push IDs similar to Firebase

Downloads

88

Readme

Unique Push ID

🆔 Generates unique, chronological, lexicographical push IDs similar to Firebase with NodeJS.

This library (with unit tests added) was directly ported from a blog post and Gist by Michael Lehenbauer of Firebase. To learn more, see "What's in a Push ID?" below.

Installation and Usage

To install, run yarn add unique-push-id or npm i unique-push-id.

Usage:

const pushId = require('unique-push-id');

const id = pushId();
console.info(id); // Will output something similar to -L9QCCdxj62CBRFCn6rF

When rapidly calling the pushId() function you can see how the IDs remain chronological and lexicographical:

const ids = [];
for (let i = 0; i < 1000; i += 1) {
  ids.push(pushId());
}
console.info(ids);
/* 
Output will look similar to:
[ 
  '-L9QCCdxj62CBRFCn6qw',
  '-L9QCCdxj62CBRFCn6qx',
  '-L9QCCdxj62CBRFCn6qy',
  '-L9QCCdxj62CBRFCn6qz',
  '-L9QCCdxj62CBRFCn6r-',
  '-L9QCCdxj62CBRFCn6r0',
  '-L9QCCdxj62CBRFCn6r1',
  '-L9QCCdxj62CBRFCn6r2',
  '-L9QCCdxj62CBRFCn6r3',
  ... more items
]
*/

Development / Testing

To develop, clone this repository and install via yarn. Tests utilize Mocha/Chai and can be ran via yarn test. The code is linted using the AirBnB coding style and is checked with eslint. Coverage can be checked via yarn coverage.

What's in a Push ID?

From Mr. Lehenbauer's blog post:

"A push ID contains 120 bits of information. The first 48 bits are a timestamp, which both reduces the chance of collision and allows consecutively created push IDs to sort chronologically. The timestamp is followed by 72 bits of randomness, which ensures that even two people creating push IDs at the exact same millisecond are extremely unlikely to generate identical IDs. One caveat to the randomness is that in order to preserve chronological ordering if a client creates multiple push IDs in the same millisecond, we just 'increment' the random bits by one."

"To turn our 120 bits of information (timestamp + randomness) into an ID that can be used as a Firebase key, we basically base64 encode it into ASCII characters, but we use a modified base64 alphabet that ensures the IDs will still sort correctly when ordered lexicographically (since Firebase keys are ordered lexicographically)."