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

acture-walkthru

v0.0.4

Published

Turn a sequence of app commands into an editable, re-renderable demo/tour artifact.

Readme

acture-walkthru

The TypeScript surface of walkthru — a Zod schema (and its inferred type) for the Demo Document, the editable, re-renderable artifact that represents a demo/tour.

The schema is generated from walkthru's Python Pydantic single source of truth, so a Demo Document produced anywhere — Python, a renderer, a capture tool — validates and types identically here.

npm i acture-walkthru

Validate a Demo Document

import { demoDocumentSchema, type DemoDocument } from "acture-walkthru";

const doc: DemoDocument = demoDocumentSchema.parse(JSON.parse(jsonString));
// Throws on unknown cue/step kinds or wrong field types — the unions are closed,
// and the wire format is camelCase (durationMs, holdAfterMs, stepId, …).

A minimal document:

const doc = {
  id: "demo-minimal",
  sections: [
    {
      id: "s1",
      steps: [
        { kind: "command", id: "step-1", command: { id: "app.open" },
          timing: { durationMs: 500 } },
      ],
    },
  ],
};
const validated = demoDocumentSchema.parse(doc); // -> typed DemoDocument

What's here / what's coming

  • Now: demoDocumentSchema (Zod validator) + the DemoDocument type.
  • Later: the live capture/play engine over acture.

The Python package walkthru owns the schema SSOT, the pure play/capture engine, and the render hand-off.

License

MIT