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

@kairotic/controls

v0.1.1

Published

Kairotic control components: knob (a rotary control) and keyboard (a virtual MIDI keyboard), with their own views in the patch

Readme

Kairotic official packages

Leer en castellano

Components that are not structural live outside the core, in packages by category, published on npm under the scope @kairotic and served inside claude.ai by jsDelivr.

| Package | Classes | |---|---| | @kairotic/synth | adsr~ [a d s r] an envelope that follows a gate · synth~ a polyphonic synthesizer | | @kairotic/spatial | pan~ [position] stereo panning · space~ [x y] binaural placement around the listener | | @kairotic/controls | knob [min max initial] [log] [name] a rotary control with its own view in the patch · keyboard [low keys] [hold] a virtual MIDI keyboard with velocity and chords, for synth~ and faust~ |

Planned: cac, notation.

In a work

Writing a class of a package (adsr~ 20 300 0.5 800) in a work that does not have it brings the whole package into the work, as one component box pinned to its version. The work stays complete and sounds the same even if the package changes later. You can also bring one by hand:

(packages)                         ; the official packages and their classes
(add-package! "@kairotic/synth")
(import! "npm:@kairotic/[email protected]/dist/index.mjs")

Writing for a package

One file per component in <package>/src/, a ClojureScript expression that evaluates to a definition (often (let [helpers …] {…})). It uses the core only through the Kairotic API, api/…, and carries its own AudioWorklet code if it needs one (api/worklet-node). Each package declares the API version it was written for ("kairotic": {"api": 1} in its package.json).

node packages/build.mjs          # every package → <package>/dist/{<component>.mjs, index.mjs}
node packages/build.mjs synth    # one

dist/index.mjs is the whole package (what a work imports); dist/<component>.mjs is each component on its own, for (import! …) of a single class.

Publishing

A GitHub release with the tag <package>-vX.Y.Z (synth-v0.1.0) publishes that package (workflow), with trusted publishing (no tokens). npm only lets a trusted publisher be set on a package that exists, so the first version of each package is published by hand once.

Licence: MPL-2.0.