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

@inbrowser/model

v0.1.0

Published

On-device LLM engine. Wraps @huggingface/transformers + ONNX Runtime Web behind a narrow Engine surface. Presets ship Gemma 4 (E2B/E4B) configurations. Adapters in subpaths satisfy @inbrowser/relay's InferenceProvider and @inbrowser/agent's LlmClient so a

Readme

@inbrowser/model

On-device LLM engine. Loads ONNX models in the browser via @huggingface/transformers + ONNX Runtime Web (WebGPU / WASM), and exposes them behind a narrow Engine surface.

Status: POC stub. Types, presets, adapter surface, and worker RPC frames are in place. The @huggingface/transformers wiring inside createEngine is not yet implemented — generate() yields an error event today. See src/engine.ts.

One-liner

import { createEngine } from '@inbrowser/model';
import { gemma4_E2B } from '@inbrowser/model/presets';

const engine = createEngine(gemma4_E2B);
await engine.ensureReady();

for await (const evt of engine.generate([
  { role: 'user', text: 'Explain WebGPU in one paragraph.' },
])) {
  if (evt.kind === 'token') process.stdout.write(evt.text);
}

Surface

| Export | What it gives you | |---|---| | createEngine(preset) | Runtime Engine — owns load state + decode loop | | definePreset(p) | Type-safe identity helper for community presets | | ModelPreset, Engine, EngineEvent, … | Public types | | @inbrowser/model/presets | gemma4_E2B, gemma4_E4B | | @inbrowser/model/relay | createLocalInferenceProvider(engine) → relay InferenceProvider | | @inbrowser/model/agent | createLocalLlmClient(engine, id) → agent LlmClient | | @inbrowser/model/worker | hostEngineInWorker(self) + connectWorkerEngine(opts) |

Vocabulary anchor

  • ONNX — model file format. ONNX Runtime Web is the execution engine (onnxruntime-web); WebGPU and WASM are its backends.
  • dtype — weight/activation precision selection (q4f16, q8, fp16, fp32). Distinct from parameter count.
  • ModelRef — bare locator (HF Hub modelId + revision).
  • ModelPreset — locator + dtype + backend + capabilities. Static.
  • Engine — runtime object owning a loaded model. Dynamic.
  • Cold start — fetch + init + warmup. Warm decode — subsequent calls on a ready engine.

Design notes

  • One factory (createEngine), many presets. No createGemmaEngine.
  • capabilities is on the preset, not the engine — interrogable pre-load (gemma4_E2B.capabilities.contextWindow).
  • EngineEvent is narrower than InferenceEvent/ChatEvent. Adapters widen.
  • Worker subpath returns the same Engine shape; the agent runtime cannot tell whether it holds a direct or remote engine.
  • Tool calling is not native to Gemma 4. The polyfill (prompt-engineered tool calling + structured-output parsing) lives in @inbrowser/agent, not here.