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

@ternlight/mini

v0.1.0

Published

On-device semantic embeddings for JavaScript — the small, fast tier. 1.58-bit BitNet-style sentence embedder via WASM. ~5.5 MB on the wire, <2 ms per embedding, no API calls.

Downloads

851

Readme

@ternlight/mini

On-device semantic embeddings for JavaScript - the small, fast tier. 5.5 MB on the wire, <2 ms per embedding, zero API calls.

A 1.58-bit (BitNet-style ternary) sentence encoder compiled to WebAssembly. Give it text, get back a 384-dimensional unit vector for semantic search, FAQ matching, deduplication, or clustering — computed entirely on the user's CPU. No network, no GPU, no ML runtime, no model download at runtime: the model ships inside the wasm.

npm install @ternlight/mini
import { embed, cosineSim, similar } from '@ternlight/mini';

// embed() → Float32Array(384), L2-normalized — compare any two with a dot product
cosineSim(embed('reset my password'), embed('I forgot my password'));   // 0.91

// or top-K semantic search over any list of strings
const results = similar('how do I reset my password', faqEntries, { topK: 3 });
// [{ text: 'Resetting a forgotten password', sim: 0.80 }, ...]

Works in Node ≥ 18, browsers (via any bundler), Cloudflare Workers, Vercel Edge, Deno, and Bun — one package, the right loader is picked automatically.

mini vs base

mini is the size/speed tier; @ternlight/base is the quality tier with the same API:

| | @ternlight/mini | @ternlight/base | |---|---|---| | Wire size (gzipped wasm) | ~5.5 MB | ~7 MB | | Embed latency (p50, M-series CPU) | 1.8 ms | 4.9 ms | | Teacher fidelity (Spearman) | 0.835 | 0.844 | | Paraphrase handling | good | noticeably stronger |

Rule of thumb: browser bundles and latency-critical UI → mini; server-side, retrieval quality, or paraphrase-heavy matching → base. Switching later is a one-line import change.

API

| Function | Description | |---|---| | embed(text) | → Float32Array(384), unit-length. Sync, <2 ms. Truncates at 128 tokens. | | cosineSim(a, b) | Cosine similarity of two embeddings (a dot product — they're normalized). | | similar(query, corpus, { topK }) | Embed query + corpus, return top-K { text, sim } sorted. | | engineInfo() | Build/model info string — dimensions, quantization format. | | TernError | Typed error (INVALID_INPUT, DIM_MISMATCH). |

For repeated searches, embed your corpus once and reuse the vectors:

const index = docs.map((d) => ({ d, v: embed(d.text) }));
const q = embed(query);
index.sort((a, b) => cosineSim(q, b.v) - cosineSim(q, a.v));

Bundler setup (browsers)

The wasm is imported as an ES module. Webpack 5 needs one flag; Vite needs the wasm plugin:

// webpack.config.js
experiments: { asyncWebAssembly: true }

// vite.config.js
import wasm from 'vite-plugin-wasm';
export default { plugins: [wasm()] };

Node needs nothing — require() or import and go.

How it works

Three ideas stacked: (1) a small transformer student is distilled from all-MiniLM-L6-v2 while being trained as a ternary model (QAT), so quantization costs almost nothing; (2) ternary weights pack to 2 bits each, putting the whole model + tokenizer + engine in one wasm file; (3) the forward pass is hand-written Rust compiled to WASM with explicit SIMD, so it runs at near-native speed in every JS runtime. Details in the repo docs.

License

MIT