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

@audio-ui/core

v0.17.1

Published

The framework-agnostic logic of audio/ui's primitives: values and scales, geometry, live sources, frame scheduling.

Readme

@audio-ui/core

The logic of audio/ui's primitives with no UI framework in it: values on a grid, linear and logarithmic scales, range geometry, live sources a view can follow outside its render cycle, and frame scheduling.

@audio-ui/react is built on it. Use it directly to build the same controls for another framework, or for the DOM alone.

npm install @audio-ui/core

It has no dependencies.

Layout

Two kinds of module are published, each as its own subpath, and the folders tell them apart:

  • primitives/<name>/: the logic of a UI primitive (a knob, a timeline, a piano roll): its controller, geometry and value handling. Imported as @audio-ui/core/<name>.
  • audio/<name>/: audio and music logic with no interface in it: analysis (spectrum, waveform peaks, filter and compressor curves, levels), device (an effect or an instrument as named parameters: state, ranges, steps, scales), pitch (notes, frequencies, pitch detection), midi (messages, files, the Web MIDI input) and time (tempo, bars and beats, ticks and seconds, the grid, the look-ahead scheduler). Imported as @audio-ui/core/<name>.

What both build on:

  • value/: scales, ranges, formatting, change and commit event details, live sources and stores
  • dom/: frame scheduling, pointer release, visibility, data attributes
  • shared/: language helpers, math, pitch names

index.ts is the public API of what the primitives share. @audio-ui/core/internal holds helpers for adapters and may change in any release.