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

ducktape-laya-browser

v0.3.0

Published

Embedded Laya decision engine for browsers (WebAssembly and WebGPU)

Readme

ducktape-laya-browser

Local Laya decisions in the browser: ask named questions about a text (choice picks one of several options, noul gives the probability that a statement is true, score picks a level on an ordered scale) and get calibrated probabilities, using the same C++ core and llama.cpp runtime as the native library, compiled to WebAssembly with an optional WebGPU build. Inference runs in a module worker. Experimental: it is tested on one browser (Chromium 152 for 0.1.0 and 0.2.0, Chrome 156 from 0.3.0) and one GPU, and its results differ slightly from native builds (platforms). 0.1.0 had a different API (see the migration notes).

npm install ducktape-laya-browser

Requirements

  • A secure context that allows module workers and WebAssembly compilation, with WASM SIMD. Serve .wasm as application/wasm.
  • WebGPU is optional: the webgpu backend needs a usable adapter and the JSPI/WASM-exceptions support of the pinned runtime.
  • The model file, served by your application. No model or CDN URL is built in.

Serve the package directory under an application URL, keeping its relative paths (a bundler may copy it into public assets).

Usage

import { Laya } from '/vendor/laya/index.mjs';

const engine = await Laya.open({
  modelUrl: '/models/Laya-Q8_0.gguf',
  sha256: 'c06528c5746d3bb8baa72a27938be95abbfd0b226f8471e8a9e365ed0bb066d2',
  backend: 'auto',
});
try {
  const result = await engine.execute({
    state: 'Please refund the duplicate charge.',
    questions: { refund: { type: 'noul', instructions: 'Does the customer request a refund?' } }
  }, { timeoutMs: 10000 });
  console.log(result.answers.refund.noul);
} finally {
  await engine.close();
}

Opening

Laya.open(options) takes the model asset and the options together. Laya.openRouter(models, options) maps route IDs to assets, { url, sha256, contextTokens, overflow, temperatures }, where a model's own settings override the shared options for that route.

| Option | Meaning | |---|---| | modelUrl, sha256 | open only: the model URL and its optional SHA-256 | | backend | wasm (default, single-threaded CPU), webgpu, or auto (WebGPU, then WASM if WebGPU initialization fails; a model asset failure is not retried) | | contextTokens | Prompt capacity: 32 up to the model's maximum (trained_context_tokens, 8,192 for the shipped files), default 512 | | overflow | Default policy for prompts over the limit: reject (default), truncate_end, truncate_start or scan | | temperatures | Calibration overrides keyed like choice, choice.3_5 or noul.2; finite and above 0 | | maxPending | Accepted calls, 1–1024, default 16 | | maxModelBytes | Total model bytes fetched, default 1 GiB | | maxLoaded | Router only: models kept loaded, 1–4, default 1 | | auto | Router only: { english, default } routes for model: 'auto' | | initializationTimeoutMs | 1–86400000, default 120000 per backend attempt; expiry rejects with status 6 | | signal | Aborts initialization (status 5) | | onDiagnostic | Receives low-level runtime text, otherwise suppressed | | moduleUrl, wasmUrl, webgpuModuleUrl, webgpuWasmUrl, workerUrl | Override asset locations |

Router requests name a route in model, or send model: 'auto' (with an optional lang) to choose by the state's language. The English (449 MB) and multilingual (658 MB) models together exceed the default maxModelBytes, so raise it to route between them. The build is wasm32 with a heap of at most 4 GiB: weights and inference buffers of every loaded model must fit, and inference memory grows with contextTokens.

engine.capabilities reports the selected backend and whether running CPU calls can be cancelled (only on cross-origin-isolated pages with the WASM backend).

Executing

engine.execute(request, options) takes one request (object or JSON string) or an array of up to 32, and resolves to parsed results. Requests are strict; besides state and questions or schema, they may set max_tokens, temperatures, overflow, max_windows, boolean_threshold (with schema), and on a router model and lang. Request objects are serialized with JSON.stringify, which reorders integer-like keys and writes 149.0 as 149; both can change the prompt and the results, so pass a JSON string when the literal text matters. Call options are signal, timeoutMs (0–86400000, counted from enqueue), onEvent and requestId, as in the Node package. After an abort or deadline settles a call, its onEvent receives no more events. await engine.info() returns runtime and model diagnostics.

Errors and closing

Every error carries status (exported as Status). Argument errors, including null or non-object options to open, openRouter, execute and close, carry status 1; queue and lifecycle failures also carry code: ERR_LAYA_QUEUE_FULL and ERR_LAYA_CLOSED (status 1), ERR_LAYA_WORKER_EXITED (status 3). A model asset that cannot be fetched or fails its sha256 rejects with status 2, assets over maxModelBytes with status 1, and an aborted signal with status 5; with backend: 'auto' these are not retried with WASM, while a WebGPU failure is. A runtime that cannot be loaded or has the wrong ABI fails with status 7 (Status.UNSUPPORTED_PLATFORM) and code ERR_LAYA_UNSUPPORTED (every status-7 error carries that code), unless the browser could not reserve its WebAssembly memory, which is status 4. Strings that are not well-formed Unicode are rejected. A GPU device loss or a runtime abort fails pending work and closes that engine; open a new one.

close() drains accepted calls and terminates the worker; close({ cancelPending: true }) cancels them first. Repeated calls return the same promise.

Deployment, failure semantics and validation are in the browser guide; the request and result format is in the API guide.