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

@stepbook/runner

v0.2.0

Published

Pure execution engine for stepbook pipelines (Node).

Readme

@stepbook/runner

The execution engine behind stepbookStorybook for typed pipelines, especially LLM ones. A stepbook pipeline is a set of typed async units you compose in code — a line for a pipeline, a loop for an agent — with optional Zod schemas, assertions, and per-unit caching. This package runs them; it has no UI.

Most people drive the runner through @stepbook/cli. You import it directly to author unit files and the pipeline entrypoint.

Install

npm install @stepbook/runner zod

Defining a unit

Each unit is a default-exported defineStep({...}) — its name is inferred from the filename, and it returns a callable you compose from the entrypoint:

import { z } from 'zod'
import { defineStep } from '@stepbook/runner'

export default defineStep({
  type: 'derive',
  schema: z.object({
    longWords: z.array(z.string()),
    density: z.enum(['concise', 'balanced', 'verbose']),
  }),
  runner: async (input: { words: string[]; wordCount: number }) => {
    const longWords = input.words.filter((w) => w.length >= 5)
    const ratio = longWords.length / input.wordCount
    const density = ratio < 0.2 ? 'concise' : ratio < 0.4 ? 'balanced' : 'verbose'
    return { longWords, density }
  },
  assertions: (o) => [
    { name: 'density is known', pass: ['concise', 'balanced', 'verbose'].includes(o.density) },
  ],
})

The entrypoint

A definePipeline({ name, runner }) composes units by calling them — no deps, the wiring is the code. stepbook run executes the runner and records every unit call as a first-class node in the run's trajectory:

import { definePipeline } from '@stepbook/runner'
import parse from './steps/parse.step'
import analyze from './steps/analyze.step'

export default definePipeline({
  name: 'demo',
  runner: async (input) => analyze(await parse(input)),
})

Step types — input | parse | llm | derive | eval — signal intent and drive the dashboard's coloring. For LLM units, ctx.report({ model, tokens, cost, latencyMs }) records telemetry the dashboard reads and stepbook run rolls up into a per-run cost.

Docs

License

MIT