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

@axiomvn/testing

v0.3.0

Published

Deterministic playthrough and coverage tools for Axiom VN stories.

Readme

@axiomvn/testing

Deterministic playthroughs, coverage, and browser instrumentation for Axiom VN stories.

A story can be driven without a browser: advanced, chosen through, recorded as a transcript, and searched to exhaustion over every state a reader can reach. That is what makes coverage over a branching story a real answer rather than a sample, what lets a change report say which paths an edit can reach, and what makes a recorded playthrough a regression test. The browser half instruments a real page, including the renderer counter that holds the canvas to drawing only when the story changes.

Depends on @axiomvn/core alone, and no engine package depends on it — the toolchain names it as an optional peer for coverage and consistency. A creator installs it when they want to test their story, which is also how @axiomvn/toolchain's two analysis commands are satisfied.

Entry points

  • @axiomvn/testing — the playthrough driver, the transcript, and coverage.
  • @axiomvn/testing/browser — the instrumentation a Playwright gate reads from a live page.

Start a project with @axiomvn/create.