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

@radajakub/plyui

v0.5.0

Published

React components that draw plybench games: a board per game, the tree of a set of games, and an LLM call.

Readme

plyui

Published on npm as @radajakub/plyui (the name plyui is too close to an existing package).

React components that draw plybench games, shared by the plybench website and plyweb (the job tracker), so a game looks the same in both.

  • Boards (GameBoard): the game as it stood after some of its moves, for every plybench game: tic-tac-toe and its variants, Magic Square and Story Magic Square, Nim and its variants and Story Nim, Connect Four, Breakthrough, Monty Hall and the bandit. Any other game is shown as its observation's text.
  • Tree (GameTree, buildTree): a set of games as one seat played them. Each node is what the seat saw when it moved, each edge a move or what followed it (chance, the opponent). An edge is as thick as its share of the node's games and says its count, its wins and, for a bandit, its win chance. One game is one path; highlight marks one game in many.

Data

Every component takes plybench's own data and fetches nothing (src/view.ts): a GameView is one game as played, in plybench's names: its game config (bandit:p=3/4;1/4;1/2,shift=1), its moves in order (seat, observation, move), the observation it ended in, its result for seat i, and the instance's params. Each site converts its data to it: plyweb from plybench's trace (plybench-trace --json), the website from its database.

Use

The components use Tailwind classes and the colour tokens both sites define: background, foreground, card, muted, muted-foreground, border, accent. A site's stylesheet scans the package so its classes are generated:

@import "tailwindcss";
@source "../node_modules/@radajakub/plyui/dist";
import { GameBoard, GameTree } from "@radajakub/plyui";

<GameBoard view={game} at={3} />          // after 3 moves; at = game.steps.length: the end
<GameTree games={games} seat="i" highlight={games[0]} />

Develop

npm install, then npm test (the parsers and the tree, in Node), npm run typecheck, npm run build (dist/, ESM and types), and npm run format. React is a peer dependency.

Release

Fill in CHANGELOG.md under [Unreleased], commit, then from the ply folder:

make release REPO=plyui VERSION=0.3.0 DRY_RUN=1   # the plan only
make release REPO=plyui VERSION=0.3.0             # release, then update and deploy the website and plyweb

It runs this repository's make release VERSION=0.3.0: checks, sets the version, dates the changelog, commits, tags v0.3.0 and pushes. The tag's Release workflow publishes to npm through trusted publishing (set on npmjs.com for this repository and release.yml; no token). Then the plybench website and plyweb get the new version, are checked, committed, pushed and deployed.