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

@mailwoman/neural-web

v5.10.1

Published

Browser-side mailwoman neural runtime. Pairs the existing tokenizer + decoder with an onnxruntime-web inference path (WebGPU primary, WASM SIMD fallback). Drop-in for @mailwoman/neural when targeting a static-asset deploy (Phase B of the demo plan).

Downloads

2,268

Readme

@mailwoman/neural-web

Browser-side mailwoman neural runtime — drop-in for @mailwoman/neural when targeting a static-asset deploy. Pairs the existing SentencePiece tokenizer + BIO decoder with an onnxruntime-web inference path (WebGPU primary, WASM SIMD fallback).

Path B of the demo plan — see sister-software/mailwoman#98.

Status

v0.1.0 — scaffold + end-to-end smoke test. WebOnnxRunner implements the NeuralRunner interface and is composable into NeuralAddressClassifier exactly like OnnxRunner from @mailwoman/neural. Test suite runs the real @mailwoman/neural-weights-en-us model through the WASM execution provider in Node — WebGPU is the production-time fast path but isn't testable in Node.

Quick start

import { loadNeuralClassifierFromUrls } from "@mailwoman/neural-web"

const classifier = await loadNeuralClassifierFromUrls({
	modelUrl: "/static/mailwoman/model.onnx",
	tokenizerUrl: "/static/mailwoman/tokenizer.model",
	runner: {
		// Optional. If your bundler doesn't put ort .wasm files in the default location,
		// point this at where you serve them.
		wasmPathsRoot: "/static/ort/",
	},
})

const tree = await classifier.parse("123 Main St, Springfield, IL 62704")
console.log(tree.roots)

For lower-level control, use WebOnnxRunner directly:

import { WebOnnxRunner, MailwomanTokenizer, NeuralAddressClassifier } from "@mailwoman/neural-web"

const runner = await WebOnnxRunner.fromUrl("/static/mailwoman/model.onnx", { useWebGpu: true })
const tokenizer = await MailwomanTokenizer.loadFromBase64(/* base64 of tokenizer.model */)
const classifier = new NeuralAddressClassifier({ tokenizer, runner })

Execution provider strategy

WebOnnxRunner attempts WebGPU first (10× faster than WASM on supported devices — Chromium 113+, Safari Tech Preview, hardware-dependent). If the WebGPU probe fails (no adapter, browser doesn't expose it, etc.), it transparently falls back to the WASM execution provider. Set useWebGpu: false to skip the probe entirely — useful in test environments where the failure path adds latency.

Bundling

This package ships compiled TypeScript only. The onnxruntime-web runtime ships its own .wasm assets — your bundler needs to serve them. The package's defaults point at a CDN; production deploys typically self-host:

import { loadNeuralClassifierFromUrls } from "@mailwoman/neural-web"

// Copy node_modules/onnxruntime-web/dist/*.wasm into your /public dir during build,
// then point the runner at them:
const classifier = await loadNeuralClassifierFromUrls({
	modelUrl: "/static/mailwoman/model.onnx",
	tokenizerUrl: "/static/mailwoman/tokenizer.model",
	runner: { wasmPathsRoot: "/ort-wasm/" },
})

Why not extend @mailwoman/neural directly?

@mailwoman/neural depends on onnxruntime-node, which ships native binaries and breaks in a browser bundle. The classifier surface itself is runtime-agnostic — it only needs a NeuralRunner (a structural interface with infer(ids): Promise<InferResult>). Splitting the runner lets both implementations co-exist without forcing browser bundlers to dead-code-eliminate native code.

License

AGPL-3.0-only.