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

@kalin-setterberg/encoding

v0.1.3

Published

Helpers for decoding or encoding BASE64 and UTF-8 in any execution context.

Downloads

7

Readme

JS functions for working with encodings. Contains typings for TypeScript.

Encode Base64

All data are processed using Uint8Arrays. In a node-like context you may encode a Buffer but the return value will be a plain Uint8Array.

import { b64enc } from "@kalin-setterberg/encoding";
const useBase64url = true;
const data = new Uint8Array([104, 101, 108, 108, 111, 32, 119, 111, 114, 108, 100]);
/** @type {Uint8Array} */
const result = b64enc(data, useBase64url);

Encode UTF-8

Prefers the use of a globally defined TextEncoder following the WHATWG standard. If no TextEncoder is defined but there is a global Buffer, as in node, a Buffer will be used for encoding.

Falls back upon a custom implementation supporting up to 16 bit code points.

import { utf8enc } from "@kalin-setterberg/encoding";
const data = "hello world";
/** @type {Uint8Array} */
const result = utf8enc(data);

Decode UTF-8

Prefers the use of a globally defined TextDecoder following the WHATWG standard. If no TextDecoder is defined but there is a global Buffer, as in node, Buffer.toString() will be used for decoding when the parameter is an instance of Buffer.

Falls back upon a custom implementation supporting up to 16 bit code points.

import { utf8dec } from "@kalin-setterberg/encoding";
const data = new Uint8Array([104, 101, 108, 108, 111, 32, 119, 111, 114, 108, 100]);
/** @type {string} */
const result = utf8dec(data);