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

blast64

v0.2.2

Published

An apparently even faster in-browser base64 decoder

Downloads

22

Readme

⚡️ blast64

Apparently the fastest way of decoding Base64 in Chrome.

Installation

npm install blast64

Usage

var blast64 = require('blast64');

// From base64 to UTF-8 string
blast64.decode(base64string);

// From base64 to Uint8Array
blast64.decode_to_array(base64string);

Testing and Benchmark

This is the average time from encoded string to UTF-8 encoded result.

The 💓 was ran 10000000 times.

The ~355kb payload was ran 1000 times.

| Load | atob+TextDecoder | js-base64 | fast64 | base64-js | blast64 | |--------|------------------|------------|-----------|-----------|-----------| | 💓 | 0.0019 ms | 0.0025 ms | 0.0031 ms | 0.0018 ms | 0.0010 ms | | ~355kb | 31.257 ms | 4.5263 ms | 2.9529 ms | 1.7501 ms | 1.3920 ms |

And this are the average times without the TextDecoder step where relevant:

| Load | fast64[0] | atob | blast64.decode_to_array | |--------|-----------|-----------|---------------------------| | 💓 | 0.0017 ms | 0.0008 ms | 0.0005 ms | | ~355kb | 2.5336 ms | 1.7580 ms | 1.0701 ms |

[0] fast64.decode(str, {uint8Array: true})

Not bad for a few hours of hacking I'd say! But it's still only decoding, would have to sit down and make it encode as well at some point.