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

@sabaki-js/doom

v1.0.0

Published

Sabaki plugin — Doom decisions (nav + combat arbitration).

Readme

@sabaki-js/doom

npm license CI

Doom decisions (navigation + combat arbitration).

Questions: command, target, weapon. Work in progress: nav MiniLM (MAP01) + vision policy (arena).

Demo

npm run demo — the plugin decides on 3 canned MAP01 states (nano, no deps).

The mini model (MiniLM + exit compass) finishes MAP01 — 4/6 EXIT:

démo : le mini finit MAP01

| mode | weights | closed loop | |---|---|---| | nano (TF-IDF, 112 terms) | src/weights.json | 0/6 | | mini (MiniLM ONNX, CPU) | sabaki-models | 2–4/6 |

Run your own demo

The classifier runs in Node, the game in Python (VizDoom). The JS server decides, the Python client plays — one HTTP call per game tick.

# 1. game + model stack (Python)
pip install vizdoom gymnasium pygame onnxruntime
git clone https://github.com/sabaki-js/doomLaya /tmp/doomlaya  # fork Apache-2.0 d'azalio/doomLaya, voir NOTICE

# 2. mini weights (~90 MB) + tokenizer
# from https://github.com/sabaki-js/sabaki-models/releases (doom_nav.onnx)
export ONNX=/path/to/doom_nav.onnx VOCAB=/path/to/tokenizer.json

# 3. JS decision server (needs sabaki@>=1.0.1 + onnxruntime-node)
npm i [email protected] onnxruntime-node
node serve_mini.mjs 8472

# 4. play one episode (second terminal)
DOOM_SERVE=http://localhost:8472 python examples/drive_serve.py 1

serve_doom.mjs serves the nano classifier instead (faster, weaker: 0/6 — it decides well on single states but cannot navigate a full level).

Usage

import { Sabaki } from "sabaki";
import plugin from "@sabaki-js/doom";

const sabaki = new Sabaki().register(plugin.default ?? plugin);
const r = sabaki.decide({ state: "..." });
// { domain: "doom", decision: ..., confidence: ..., plugin: "@sabaki-js/doom" }

Ask another question with input.question.

Part of sabaki — see the GUIDE.

License

MIT