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

@out-of-order/trace

v0.5.0

Published

Drop a visual overlay on any page: numbered tab stops, the path between them, and a11y findings ringed in place.

Readme

@out-of-order/trace

npm downloads bundle size

⚠️ Under heavy development. Released, but the API is still changing and may break between versions.

Drops a visual overlay on any live page: every tab stop gets a numbered badge, each hop between stops is drawn as a line (red when it runs against reading order), and every accessibility finding is ringed in place with a tooltip spelling out the accessible name, role, and rule.

It is a thin visual layer over @out-of-order/core: the analysis comes entirely from audit, so the same verdicts you assert in tests are what you see on screen.

import { trace } from "@out-of-order/trace";

const overlay = trace();
// ...
overlay.destroy();

API

function trace(options?: TraceOptions): TraceHandle;

interface TraceOptions {
  /** Subtree to analyze. Defaults to document. */
  root?: Document | Element;
  /** Forwarded to audit (rule toggles and custom rules). */
  audit?: AuditOptions;
  /** Motion behaviour: "auto" | "on" | "off". Defaults to "auto". */
  motion?: MotionMode;
  /** Modifier that toggles overlay click-through ("peek"). Defaults to "Alt". */
  peekKey?: ModifierKey;
  /** Mount the floating in-page control panel. Defaults to true. */
  controls?: boolean;
  /** Called after every re-analysis with the fresh result. */
  onResult?: (result: AuditResult) => void;
  /** Called whenever visibility or peek flips, whatever flipped it. */
  onStateChange?: (state: { visible: boolean; peeking: boolean }) => void;
}

interface TraceHandle {
  /** Whether the overlay is currently shown. */
  readonly visible: boolean;
  /** Whether the overlay is currently click-through ("peek"). */
  readonly peeking: boolean;
  /** Show or hide the whole overlay: badges, arrows, and the element rings. */
  setVisible(visible: boolean): void;
  /** Flip between shown and hidden. */
  toggle(): void;
  /** Turn peek (click-through) on or off. Ignored while the overlay is hidden. */
  setPeek(peek: boolean): void;
  /** Switch the motion behaviour. */
  setMotion(mode: MotionMode): void;
  /** Remove the overlay layer, observers, and listeners. */
  destroy(): void;
  /** Latest analysis result, or null before the first draw. */
  result: AuditResult | null;
}

The overlay re-analyzes itself on DOM mutation, so most pages need nothing beyond the mount.