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

@action-flow/scenario

v0.1.0

Published

Isolated, typed debug scenarios for ActionFlow

Readme

@action-flow/scenario

Typed debug scenarios for @action-flow/core. Requires a Runtime created with environment: "development", environment: "test" or an explicit allowDebug: true.

npm install @action-flow/core @action-flow/scenario
import { createRuntime, defineAction, defineModule } from "@action-flow/core";
import { createScenarioRunner } from "@action-flow/scenario";

const runtime = createRuntime({
  providers: {}, environment: "development",
  modules: [defineModule("math", { double: defineAction({ handler: (n: number) => n * 2 }) })],
});
const runner = createScenarioRunner(runtime);
const scenario = runner.defineScenario({ id: "double", action: "math.double", input: 3 });
const result = await runner.run(scenario);
if (result.status === "success") console.log(result.output); // number: 6

Definitions support providers, mocks, setup, cleanup and mutually exclusive input / inputFactory. Input and return mocks are checked against the selected registered Action. providers and mocks can be async factories receiving a per-run context. A provider factory initially sees the Runtime's base providers; subsequent hooks see the scoped bindings. Call ctx.defer(release) immediately after allocating a fixture to release it even if setup later fails.

runner.runtime exposes the associated Runtime. runner.run(definition, { onTrace }) streams this run's live events only; synchronous and asynchronous observer failures are isolated. The separate @action-flow/devtools package uses this interface for its browser panel. Scenario does not import DevTools or access DOM globals.

Overrides and mocks propagate to nested Dispatch through an execution scope. They never replace Runtime bindings or handlers. Static objects retain their business object references; use factories for fresh mutable providers, inputs and mock values on repeated or concurrent runs. Overrides replace top-level bindings and are not deep merged or cloned.

The runner drains all started descendants before cleanup, then calls definition cleanup (if setup was entered) and all deferred releases in reverse order. Cancellation is cooperative and does not force a pending handler or hook to settle. Escaped calls made after scope closure reject. A caught or detached child failure stays in the trace; the root outcome determines execution success.

Results include status, scenarioId, runId, optional root IDs, a bounded local trace, droppedRecords and cleanupErrors. Failures preserve the thrown value. Cleanup failures return an AggregateError containing the primary failure (if any) followed by cleanup errors, and set status to error. Invalid/foreign definitions and disabled debug execution reject before lifecycle callbacks. The local trace defaults to 1,000 records and no payload capture, independently of Runtime retention and capture settings; configure createScenarioRunner(runtime, { trace: ... }) when needed.

ESM only. The sole runtime dependency is @action-flow/core. This package does not manage application state. Production debug opt-in is an execution policy, not authentication or a security boundary for an exposed remote endpoint. See the changelog for 0.x API changes.