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

@caputchin/engine-kit

v0.5.0

Published

Optional authoring kit: the reducer-to-run adapter (fixed-step replay loop + default trace codec) for Caputchin server-validated game replay

Downloads

343

Readme

@caputchin/engine-kit

The reducer-to-run authoring lane for Caputchin server-validated game replay. Write your game as a pure reducer and this kit turns it into the one conforming run(seed, config, trace) the platform replays. It is optional: you can ignore it and ship a bare run you wrote by hand against @caputchin/replay-contract.

This kit exports only its own surface and re-exports nothing. Install the pieces it builds on directly, from their owners:

What it provides

  • defineEngine(spec) - declare your reducer (init / step / tick / isOver / result, plus an optional render view). A typed identity helper; it wraps nothing.
  • toRun(engine, { maxTicks }) - the adapter: turns the reducer into the conforming run(seed, config, trace). This is the kit's reason to exist.
  • replay - the fixed-step loop that drives both live play and the server replay, so live score equals replay score by construction.
  • encodeTrace / decodeTrace - the batteries-included JSON trace codec (opaque to the platform; bring your own if you prefer).
  • FIXED_TIMESTEP_MS, CODEC_V and the reducer types (EngineDef, TickInput, Result, ...).
  • caputchin-selfcheck (CLI bin) - probe a built run artifact for determinism before publish: caputchin-selfcheck dist/run.js.

Usage

import { defineEngine, toRun } from '@caputchin/engine-kit';
import { rng, capMath } from '@caputchin/determinism';

const engine = defineEngine<State, Action, Config>({
  init: ({ seed }) => ({ rngState: rng(seed).state, score: 0 /* ... */ }),
  step: (s, action) => ({ /* apply one input */ }),
  tick: (s) => ({ /* advance one fixed step */ }),
  isOver: (s) => s.score >= s.goal,
  result: (s) => ({ score: s.score, passed: s.score >= s.goal }),
});

// The one mandatory export the artifact ships:
export const run = toRun(engine, { maxTicks: 2000 });

Then, before publishing, prove it is deterministic:

caputchin-selfcheck dist/run.js

Determinism is the author's burden

The kit gives you the loop and the adapter; cross-environment float determinism is yours. Use rng / capMath from @caputchin/determinism for randomness and transcendentals, keep wall-clock and Math.random out of the sim, and the live run and the server replay agree bit-for-bit.