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

@actor-web/testing

v0.1.0

Published

Testing utilities for actor-core applications including state machine analysis

Readme

@actor-web/testing

Testing utilities for Actor-Web applications.

Actor-Web behaviors can be driven by XState machines (defineBehavior().withMachine(...)). This package helps you test those machines structurally — finding unreachable states and reporting transition coverage — so a state can't silently become dead code.

Install

pnpm add -D @actor-web/testing

API

analyzeStateMachine(machine): StateAnalysisResult

Statically analyze a machine and return how many states it defines, how many are reachable, and which (if any) are unreachable.

import { analyzeStateMachine } from '@actor-web/testing';

const result = analyzeStateMachine(compareMachine);
// result.totalStates, result.reachableStates, result.unreachableStates

analyzeStateMachineWithGraph(machine): Promise<StateAnalysisResult>

A deeper, graph-based analysis (via @xstate/graph) that explores transitions to compute reachability more precisely. Async.

assertNoUnreachableStates(machine, machineName?): void

Test assertion — throws if the machine has any unreachable states. Drop it into a unit test to guard a machine against dead states:

import { assertNoUnreachableStates } from '@actor-web/testing';

it('has no unreachable states', () => {
  assertNoUnreachableStates(compareMachine, 'compare');
});

generateCoverageReport(machine, machineName?): string

Return a human-readable coverage report (reachable / total states, percentage, and the unreachable list) for logging or snapshotting.

StateAnalysisResult

interface StateAnalysisResult {
  totalStates: number;
  reachableStates: number;
  unreachableStates: string[];
  // ...
}

See also