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

@sigx/actors-dashboard

v0.9.2

Published

The web dashboard for @sigx/actors — hosts, actors, latency, errors and cluster topology as embeddable sigx components

Readme

@sigx/actors-dashboard

The web dashboard for @sigx/actors: hosts, actors, latency, errors and cluster topology, as embeddable sigx components. The five tabs sigx actors top has, in a browser.

pnpm add @sigx/actors-dashboard @sigx/actors-monitor
import { ActorsDashboard } from '@sigx/actors-dashboard';
import { httpSource } from '@sigx/actors-monitor';

<ActorsDashboard source={httpSource({ url: '/admin/ops' })} />

Every panel is also exported on its own — OverviewPanel, HostsPanel, HostPanel, ActorsPanel, ClusterPanel, HealthPanel — so a portal can embed one table instead of the whole shell. mountActorsDashboard(el, opts) renders it into a page that is not a sigx app.

Styling is self-contained and themed by --sigx-actors-* custom properties: override the tokens on any ancestor and the whole dashboard follows.

Two things to get right

Never put the ops secret in the browser. /admin/ops above is a route of your app, not the host's. ops() sets no CORS headers and refuses to construct without a bearer token outside dev — it reports your actor type names, traffic shape and cluster topology, and actor keys are user data. Point httpSource at a same-origin route you own, which authenticates the operator however your app already does and forwards to ops() with the bearer attached server-side.

A counter going backwards is a gap, not a rate. That rule, and the rest of what makes these numbers honest, lives in @sigx/actors-monitor — this package renders its verdicts and re-derives none of them, which is what keeps it from disagreeing with the CLI.

Peer dependencies: @sigx/actors (≥ 0.9), plus @sigx/runtime-core, @sigx/runtime-dom and @sigx/reactivity (all ≥ 0.15).

npm ≥ 7 and pnpm ≥ 8 install peers automatically, so the install line above is usually all you need — but that is a package-manager default, not a guarantee, and Yarn Classic and anyone running auto-install-peers=false will not get them. If the app fails to start with Cannot find package '@sigx/actors', install it explicitly:

pnpm add @sigx/actors

It is needed because the host drill-down decodes that host's own latency histogram with core's percentile walk rather than reimplementing it — duplicating that walk is how a cluster-wide p99 quietly stops matching the per-host one. @sigx/actors is WinterCG-clean and zero-dependency, so it tree-shakes to the walk itself.

Requires Node ^20.19.0 || >=22.12.0 to build, and any modern browser to run.

Documentation

https://sigx.dev/actors/

Source, examples and architecture notes: https://github.com/signalxjs/actors

MIT © Andreas Ekdahl