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

@waveform-playlist/playout

v12.5.4

Published

Playout engine for waveform-playlist using Tone.js

Readme

@waveform-playlist/playout

Tone.js-based PlayoutAdapter for @waveform-playlist/engine — drives playback, recording, and effects on a shared global Tone.js audio context. Used by @waveform-playlist/browser (the React surface). For native Web Audio (no Tone.js), see @dawcore/transport.

Installation

npm install @waveform-playlist/playout

Requires tone (^15.0.0) as a peer dependency — this package doesn't bundle Tone.js, so the version in your app is the one that runs. @waveform-playlist/engine is an optional peer; most consumers pull in both automatically via @waveform-playlist/browser rather than installing this package directly.

Usage

import { createToneAdapter } from '@waveform-playlist/playout';
import { PlaylistEngine } from '@waveform-playlist/engine';

const adapter = createToneAdapter();
const engine = new PlaylistEngine({ adapter });

engine.setTracks(tracks); // ClipTrack[]
engine.play(0);

createToneAdapter() eagerly creates the shared global Tone.js context before building its audio graph, so adapter.audioContext is guaranteed to be the same context the playout's nodes are on.

Audio context is a standardized-audio-context ponyfill

getGlobalContext() / getGlobalAudioContext() return Tone.js's global context, whose rawContext is always a standardized-audio-context ponyfill — not a native BaseAudioContext / AudioContext. This is deliberate: the ponyfill normalizes cross-browser differences (e.g. Firefox AudioWorkletNode / AudioParam).

Consequences for integration:

  • getGlobalAudioContext() instanceof window.AudioContext is false.
  • The native AudioWorkletNode constructor rejects it — new AudioWorkletNode(getGlobalAudioContext(), 'my-processor') throws TypeError: parameter 1 is not of type 'BaseAudioContext' (same in Chrome and Firefox).

Third-party worklet code should not hardcode the native constructor. Inject the AudioWorkletNode constructor and the module loader (the dependency-injection pattern from chrisguttandin/limiter-audio-worklet — paired with limiter-audio-worklet-processor), or import AudioWorkletNode from standardized-audio-context, so the code works on a native or ponyfilled context. @waveform-playlist/worklets follows this exact pattern:

// caller supplies addModule for whichever context type is in use
await addRecordingWorkletModule((url) => ctx.audioWorklet.addModule(url));

If you genuinely need a native AudioContext, own it yourself via the web-components adapter surface (@dawcore/*), which uses native Web Audio rather than Tone.

License

MIT