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/devtools

v0.1.0

Published

Local browser DevTools for ActionFlow Runtime and Scenario

Readme

@action-flow/devtools

An explicitly mounted browser panel for ActionFlow. Lists and searches registered Actions, edits JSON inputs, runs Actions or Scenarios, and displays results, history and live nested traces with cancellation.

npm install --save-dev @action-flow/devtools
import { mountDevTools } from "@action-flow/devtools";

// runtime is a development/test Runtime; runner is optional and belongs to it.
const tools = mountDevTools({
  target: document.getElementById("devtools")!, runtime, runner,
  initialPayloads: { "session.start": '{"name":"Ada"}' },
});
// On teardown: remove the panel, request cancellation, and drain started work.
await tools.unmount();

Import it only from your application's development entry. Importing the package does not read DOM globals, mount a panel, register globals or modify the Runtime. Core and Scenario never import DevTools. Production mounting/execution is disabled by the Runtime's default debug policy; allowDebug is explicit opt-in, not authentication for a remote interface.

The UI uses native DOM elements in an isolated Shadow DOM and has no UI framework dependency. Each run gets its own scope and bounded trace. Scenario events come from its per-run onTrace observer. Runtime Middleware and base Providers are preserved; direct Action execution can still affect real injected services. Scenario definitions keep their configured input and fixture lifecycle. JSON parsing validates syntax only; business input validation remains in the Handler/application.

Defaults: 20 retained runs (maximum 100), 200 retained records per run (maximum 1,000), and 100,000 input characters. Completed runs are evicted first; new runs reject if active runs fill capacity. Clear keeps active work. Truncated traces show a notice and promote orphaned children to visible roots. Up to 40 nested tree levels are rendered; inspect the retained trace through the controller for deeper chains.

Results/errors are detached bounded snapshots using Core's snapshotTraceValue: common sensitive keys are redacted, getters/toJSON are not called, stacks are excluded, and AggregateError constituents remain inspectable. No raw business result references are retained. Trace payload capture defaults off for direct runs and follows the supplied Runner for Scenarios; the UI does not silently enable it. trace.capture and trace.redact configure direct-run trace details, while the result view uses the standard snapshot policy. Data is displayed as text and is not persisted or sent over the network.

For a custom frontend, createDevToolsController({ runtime, runner?, maxRuns?, trace? }) exposes actions, scenarios(), runs(), subscribe(), runAction(id, jsonText?), runScenario(id), cancel(id), clear() and dispose(). Its dynamic Action IDs are checked against the Registry before execution. Subscribe receives changes to immutable snapshots; observer errors cannot affect work. Dispose stops observation and requests cooperative cancellation, then waits for all started work. Uncooperative tasks can delay disposal.

ESM only. Runtime dependencies: Core and Scenario, with no UI framework. See the changelog for 0.x API changes.