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

@blunderon/bot

v0.1.0

Published

Human-like chess opponent behind a transport-agnostic interface

Readme

@blunderon/bot

This package owns the human-like chess opponent: the rating-bucketed opening book, the bundled Maia-3 model, and the Bot interface every caller depends on.

It does not own game rules, game state, matchmaking, ratings, rewards, or HTTP.

It ships TypeScript source and runs its engine in a Bun worker, so it requires Bun.

createBot() runs the engine in a worker thread. Inference blocks the thread it runs on — a single predict call stalls an event loop for tens of milliseconds — so keeping it off the caller's thread is the reason the worker exists, not an optimisation. Requests are correlated by id and time out independently; a crashed worker fails only its in-flight requests and the next call spawns a replacement.

Callers see nothing but Bot, so the same app runs against an in-process engine today and a network-backed one later without touching game code.

The engine plays the opening book while it has an entry for the position and the bot's rating bucket, then defers to the model. Model moves are validated against the caller's legal move list before they are returned.

Terminating a worker that has loaded onnxruntime-node panics Bun 1.3.14, so close() releases the worker without terminating it and the thread exits with the process. BotWorker therefore has no terminate.