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 🙏

© 2026 – Pkg Stats / Ryan Hefner

inkling-wasm

v0.1.5

Published

WebAssembly bindings for inkling: reveal ASCII art as a progress indicator in the browser.

Readme

inkling (WebAssembly)

Reveal ASCII art as a progress indicator, in the browser. The same pure Rust core as the inkling crate, compiled to WebAssembly with wasm-bindgen.

inkling

The browser has no terminal, so this exposes the engine's model rather than a renderer: parse art, choose an ordering, and read back the per-cell reveal ranks. Your JavaScript draws each frame however it likes, which is exactly how the native renderers work.

npm install inkling-wasm
import init, { Reveal } from "inkling-wasm";

await init();
const reveal = new Reveal(art, "geodesic"); // or "auto", "top", "left", ...
const glyphs = reveal.glyphs();             // width*height chars, row-major
const ranks = reveal.ranks();               // Float32Array, -1 for background

// a cell is visible exactly when its rank is in 0..=progress
function frame(progress) {
  let out = "";
  for (let i = 0; i < ranks.length; i++) {
    out += ranks[i] >= 0 && ranks[i] <= progress ? glyphs[i] : " ";
    if ((i + 1) % reveal.width() === 0) out += "\n";
  }
  return out;
}

Building

cargo install wasm-pack
wasm-pack build --target web    # emits pkg/ with inkling.js + inkling_bg.wasm

Then import the module from pkg/, or use the published npm package.

The inkling family

This is the browser (WebAssembly) build. The same engine ships five ways:

  • inkling-wasm on npm (this package), the WebAssembly build for the browser.
  • inkling-loader on crates.io, the Rust library. cargo add inkling-loader.
  • inkling-cli, the inkling command, to drive a reveal from any language through a pipe.
  • inkling-loader on PyPI, the Python package. pip install inkling-loader.
  • inkling-loader on npm, the Node addon. npm install inkling-loader.

Built from the inkling Rust core. License: MIT.