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

indexer-web

v1.0.0

Published

Search engine core for indexing text files with high performance.

Readme

indexer-web

High-performance inverted index for large text files, powered by Rust + WebAssembly and designed to work efficiently in browsers, Web Workers, and PWA.

Indexer processes data incrementally (streaming) and supports files from MBs to multiple GBs without blocking the main thread.

Features

  • Very fast text indexing (Rust + WASM)
  • Runs inside Web Workers (non-blocking UI)
  • Supports URL, Blob, and Uint8Array
  • Handles hundreds of MB / GB-scale files
  • Inverted index (term → documents + frequency)
  • High-level JS API and low-level WASM access
  • Ready for PWA usage

Installation

npm install indexer-web

Quick Start (High-level API)

import Indexer from "indexer-web";

const indexer = new Indexer();

// Index a document
const docId = await indexer.read(
  "my-worker",          // worker name (internal)
  "Large document",     // document title (stored in index)
  "/huge-text-file.txt" // URL / Blob / Uint8Array
);

// Search
const results = await indexer.search("my-worker", "example", 10);

console.log(results);
/*
[
  { doc_id: 0, count: 42 },
  ...
]
*/

// Get document title
const title = await indexer.getTitleDocument("my-worker", docId);
console.log(title);

High-level API

read(
  workerName: string,
  title: string,
  data: string | Uint8Array | Blob,
  onProgress?: (workerName: string, processedBytes: number) => void
): Promise<number>

Parameters

| Name | Description | | :----------: | :---------------------------------------: | | workerName | Identifier of the worker instance | | title | Document title (required by core indexer) | | data | URL, Blob, or Uint8Array | | onProgress | Optional progress callback |

search(
  workerName: string,
  query: string,
  limit?: number
): Promise<EngineValue[]>

Searches for a term in the indexed documents.

getTitleDocument(
  workerName: string,
  docId: number
): Promise<string>

Returns the document title.

clear(workerName: string): void

Terminates the worker and frees memory.

clearAll(): void

Terminates all workers.

EngineValue

interface EngineValue {
doc_id: number;
count: number;
}
  • doc_id – document identifier
  • count – number of occurrences in that document

Low-level API (WASM)

For advanced use cases you can access the WASM engine directly (no workers, no streaming wrapper).

import init, { Engine } from "indexer-web/dist/indexer_web";

await init();

const engine = new Engine();

const docId = engine.begin_document("Title");
engine.add_content(new Uint8Array(data));
engine.flush();

const results = engine.search("example", 10);

When to use low-level API?

  • Custom worker orchestration
  • Node.js native usage
  • Full control over memory & streaming
  • Advanced experimentation

Low-level API runs synchronously and may block the main thread.

Why Web Workers?

Indexing large files can take seconds. Workers ensure:

  • No UI freeze
  • Smooth progress reporting
  • Safe execution in browsers and PWAs

PWA Support

Indexer works in:

  • Browser
  • Web Workers
  • Progressive Web Apps (PWA)

Service Worker integration is possible and planned.

Notes & Limitations

  • Text is tokenized using ASCII rules
  • Tokens shorter than 3 characters are ignored
  • Case-insensitive (ASCII lowercase)
  • Designed for text files, not binary formats

License

MIT © Mateusz Krasuski