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

v1.1.0

Published

Acture devtools inspector — registry contents, dispatch log, when-clause evaluator, tier filter preview. Embeddable React component for dev builds.

Readme

acture-devtools

acture is a development tool first. This is dev/build-time tooling — it never becomes a runtime dependency of the apps it serves, and using it is entirely optional. See docs/positioning.md.

Embeddable React Inspector + dispatch-log instrumentation for acture registries. Dev-only — production builds skip the imports and tree-shake to nothing.

Install

pnpm add -D acture-devtools

Mount the Inspector

import { Inspector, instrumentRegistry } from 'acture-devtools';
import { registry } from './registry';

// Instrument once at module load so every dispatch is captured.
// Idempotent — re-imports do not re-wrap.
const dispatchLog = instrumentRegistry(registry);

function App() {
  const [showInspector, setShowInspector] = useState(false);
  return (
    <>
      <YourApp />
      <button onClick={() => setShowInspector((v) => !v)}>
        {showInspector ? 'Hide' : 'Show'} inspector
      </button>
      {showInspector ? <Inspector registry={registry} log={dispatchLog} /> : null}
    </>
  );
}

Three tabs:

  • Commands — list of registered commands with tier badges, filterable by tier (stable / experimental / deprecated / internal) and free-text search.
  • Dispatch log — ring-buffered most-recent-first list of every registry.dispatch call, with params, result, and duration. clear button. Default capacity 200 entries.
  • When evaluator — small REPL: type a when-clause DSL string and a JSON context, see the evaluation result update live.

Theming

No bundled UI kit. The component uses inline styles only. Theme via the data-acture-devtools-* attributes:

[data-acture-devtools-inspector] { font-family: 'Your Font', monospace; }
[data-acture-devtools-tabbar] button { background: var(--your-bg); }
[data-acture-devtools-commands] table { /* ... */ }

instrumentRegistry(registry, options?)

Wraps registry.dispatch to capture every call. Returns a DispatchLog with:

  • entries: readonly DispatchLogEntry[] — most recent at the end.
  • subscribe(listener): unsubscribe — fires on each new entry.
  • clear() — drop all entries.

Options:

  • maxEntries?: number — ring-buffer size, default 200.

Idempotent: calling twice on the same registry returns the same log. The mutation is local to this package; production builds simply don't call instrumentRegistry and pay zero runtime cost.

See acture-hard-donts §6 for why dev-only registry mutation is allowed when core React-coupling is not.

enableTierWarnings(registry, options?)

Wraps registry.dispatch to emit a once-per-command console.warn on the first dispatch of each @experimental command in a process — a nudge that an unstable surface is being exercised.

import { enableTierWarnings } from 'acture-devtools';
import { registry } from './registry';

enableTierWarnings(registry);

Options:

  • enabled?: boolean — force on/off. Default: auto — suppressed when ACTURE_SUPPRESS_EXPERIMENTAL_WARNINGS=1 is set in process.env.
  • warn?: (message: string) => void — custom sink. Default: console.warn.

Returns a disposer that restores the original dispatch. Idempotent: calling twice returns the same disposer.

Like instrumentRegistry, this is dispatch instrumentation — it observes dispatch without changing its semantics — so it lives here, not in acture core. The core stays the minimal primitive (registry + dispatcher + schema bridge + state-adapter interface); anything that wraps dispatch to observe it is an opt-in devtools concern. The agent-written equivalent is a few lines around registry.dispatch; see docs/hand-written-registry.md.