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

@root/uuid

v1.0.1

Published

Lightweight, no nonsense, 2x faster uuid.v4. 0 deps, of course.

Downloads

30

Readme

@root/uuid.js

About Lightweight, no nonsense, 2x faster uuid.v4. 0 deps, of course.

Just for node. Pre-allocates crypto.randomBytes() to achieve insane speeds without increasing the complexity. The only possible downside is that it uses a constant 31*128 bytes of memory, but this is offset by the fact that there's far less garbage collection.

Usage

npm install --save @root/uuid
var UUID = require("./uuid.js");
UUID.v4();
// f6d40277-1e32-4905-8fe6-82f40dc03b73

Rationalé

This is started out as a curiosity, pasted as a gist but now, years later, I've come back to it because it's easy to read and understand (for me, at least).

There are too many of these uuid modules out there and they're too complicated.

node-uuid vs crazy-uuid vs fast-uuid

Everybody knows about node-uuid and that it's pretty fast, right?

And everybody knows about 140byte-uuid and that it's insanely small, but really slow, right?

Well, while I was looking at all that math in node-uuid, I wondered to myself: Is that really all that more efficient than just accessing strings? (BTW, I was totally looking at the wrong function)

So I set out on a mission to make 'if' blocks and strings faster than bitwise operations, and I did! Over 2x faster! (generally in the range of 550,000/s instead of 250,000/s)

How is it 2x faster!?!?

Note that the huge time saver here is actually pooling crypto.randomBytes() ahead of time. If we were to implement the same thing in node-uuid we might see an even bigger increase.

License

Copyright 2021 The Root Group, LLC
Copyright 2015-2021 AJ ONeal

This Source Code Form is subject to the terms of the Mozilla
Public License, v. 2.0. If a copy of the MPL was not distributed
with this file, You can obtain one at https://mozilla.org/MPL/2.0/.