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

@bebeal/data-evals

v0.0.4

Published

TypeScript framework for building data evals with WebAssembly. Write compute-heavy logic in C -> compile to WASM -> call from TypeScript

Readme

@bebeal/data-evals

TypeScript framework for data evals with WebAssembly support. Write compute-heavy logic in C -> compile to WASM -> call from TypeScript

Quick start

npm install
npm run build
npm run test

Expected output

=== TypeScript Eval ===
Input: 1200
Computed: 419126400
Metrics: { matrixSum: 419126400 }
Time: 2976.38ms
✓ TypeScript test passed

=== WASM Eval ===
Input: 1200
Computed: 419126400
Metrics: { matrixSum: 419126400 }
Time: 1594.09ms
✓ WASM test passed

✅ WASM is 1.87x faster

Usage

TypeScript Eval

import { TsEval } from '@bebeal/data-evals';

class MyEval extends TsEval<string, number, { score: number }> {
  compute(input: string): number {
    return input.length;
  }

  analyze(input: string, computed: number): { score: number } {
    return { score: computed * 2 };
  }

  render(input: string, computed: number, metrics: { score: number }): string {
    return `<div>Length: ${computed}, Score: ${metrics.score}</div>`;
  }
}

const eval = new MyEval();
const result = eval.run("hello"); // { computed: 5, metrics: { score: 10 }, html: "..." }

WASM Eval

import { WasmEval } from '@bebeal/data-evals';

class MyWasmEval extends WasmEval<string, number, { score: number }> {
  render(input: string, computed: number, metrics: { score: number }): string {
    return `<div>Result: ${computed}</div>`;
  }
}

const eval = new MyWasmEval();
await eval.init('./my_wasm.js');
const result = eval.run("test");

C Interface

Default: WasmEval uses ccall with string I/O. C functions take char* input and return char* output:

char* compute(char* input) {
    // Your code here
    return result_string;
}

char* analyze(char* input, char* computed) {
    // Return JSON string
    return "{\"score\":42}";
}
emcc file.c -o wasm.js \
  -s EXPORTED_FUNCTIONS=["_compute","_analyze"] \
  -s EXPORTED_RUNTIME_METHODS=["ccall"] \
  -s MODULARIZE=1 -O3

Custom: Override compute(), analyze(), or render() to interact with WASM however you want

Requirements

WASM tests require Emscripten:

# macOS
brew install emscripten

# Linux
apt install emscripten        # Ubuntu/Debian
dnf install emscripten        # Fedora
pacman -S emscripten          # Arch

# Windows
choco install emscripten      # or: winget install emscripten

# Any platform (emsdk)
git clone https://github.com/emscripten-core/emsdk.git && cd emsdk
./emsdk install latest && ./emsdk activate latest && source ./emsdk_env.sh