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

@msb235/blits-panel

v1.4.0

Published

A debugger window for blits: every mix on the page, its voices and subjects, channels plotted over time, and a clock to pause, step and scrub

Readme

@msb235/blits-panel

A debugger window for blits. It finds every mix on the page, plots the channels of a subject you pick, and takes a mix's clock so you can pause it, step it a frame at a time and scrub it back and forth.

npm install -D @msb235/blits-panel
import { mount } from '@msb235/blits-panel';

if (import.meta.env.DEV) mount();
// …then make your mixes.

Call mount() before the app makes its mixes. Mixes made after it keep 10 s of history, which scrubbing back needs; a mix made earlier can only be paused and stepped forward. The panel says which applies to the mix you are looking at.

The panel lives in a shadow root, so the app's styles and the panel's stay apart, and it works whatever the app is built with. mount() returns a function that takes it off the page again and gives back any clock it holds.

What it shows

  • The pill: the mix's name, hold (⏸), step (⏭), a scrub bar, ⤢ to open the window, and the mix clock.
  • The window:
    • Top bar: a mix picker, the same clock controls, and a rate for a held mix.
    • Left side: the mix's subjects, which you can filter, and its voices with their state and their weight on the picked subject.
    • Right side: the picked subject's channels, then each voice's weight. A color channel, blend modes included, is a strip of the color it shows, with a thin strip per layer under an ordered mode; an affine channel is its parts (x, y, rotate, skew, scaleX, scaleY); any other channel is one plot per number. A plot is marked "read, not shown" when the app did not read the subject that frame, so the panel read it.
    • The plan, above the plots: what the mix has scheduled around now, a lane per voice track with each of its voices a bar on it, and a lane of its own for a voice with none. A tick marks each of a voice's marks, and a dashed line each mark the host announced.
    • ◯ circles, beside the voices: draws each bounded voice's circle (its within, or its around weight's) on the page, in the voice's hue. A bounded voice is marked ◯ in the list.

Holding a mix holds every mix on the same transport. Nothing the panel does while holding goes on the mix's tape, and freeing the hold lets the mix carry on from where the panel left it.

Picking a subject

Pick from the list, or press ◎ pick and click the subject on the page; Escape cancels. A subject that is a DOM element, or contains the element you click, is found on its own. For anything the DOM cannot see, such as a three.js object, pass the app's own lookup:

mount({
  pick: (x, y) => objectUnderPointer(x, y), // client coordinates in, a subject out
  outline: (subject) => screenBoxOf(subject), // optional: a DOMRect to outline it by
});

offer({ pick, outline, screen }) hands over the same functions without mounting anything, so the blits DevTools extension can pick in the scene too.

Subjects are named by the mix's labelOf option where it has one, and otherwise by their name or id, a DOM element's tag, or their class and a number.

Options

| Option | Default | What it does | |---|---|---| | history | 10000 | How far back mixes made after mount() can scrub, in ms. false adds no history. | | pick | none | Finds the subject under a point, for subjects the DOM cannot see. | | outline | none | Where a subject is on screen, so hovering it can outline it. | | screen | the same numbers | Where a point in the positions given to mix.plot is on screen, in client coordinates, so a bounded voice's circle lands in the right place. |

The two halves

The window never touches a mix. It talks to a Source: events up from the page and commands down to it, all plain data. agent() is the page side and Panel the window. mount() joins them in one page. Across a channel, serve(agent(), wire) runs on the page side and wireSource(wire) on the panel's, where a Wire is anything that sends and receives strings; the blits DevTools extension in apps/devtools does this.