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 🙏

© 2025 – Pkg Stats / Ryan Hefner

web-audio-instrumentation

v1.0.1

Published

Instrumentation for Web Audio API

Readme

web-audio-instrumentation

The backbone of Web Audio Tools. Instruments methods in the Web Audio API and emits events for all activity of state.

Caveats

This library needs to maintain an internal, iterable list of AudioNodes created in the context. This means all the nodes are strongly held, and never GC'd. Obviously a big problem for complex applications, but this is mostly for debugging.

API

new WebAudioInstrumentation()

Creates a new instance of the WebAudioInstrumentation. Inherits from EventEmitter.

core.instrument(global)

Prepares the core to patch AudioContext, AudioNode and AudioParam methods. Generally, global will be the window object, but can be any object that has properties AudioContext, AudioNode and AudioParam. Must be called before any action on the Web Audio API in order to track state.

core.getNode(nodeOrID)

Takes either an AudioNode or an ID (created by the instrumentation), and returns an AudioNodeModel. This is mostly used internally.

event: "create-node"

  • node: AudioNodeModel

event: "connect-node"

  • source: AudioNodeModel
  • dest: AudioNodeModel
  • output: Number
  • input: Number

event: "connect-param"

  • source: AudioNodeModel
  • dest: AudioNodeModel
  • paramName: String
  • output: Number

event: "disconnect-node"

  • source: AudioNodeModel
  • output: Number

event: "schedule-automation"

  • node: AudioNodeModel
  • paramName: String
  • eventName: String
  • args: Array

Example

var WebAudioInstrumentation = require("wa-tools-core");
var core = new WebAudioInstrumentation();
core.instrument(window);

core.on("create-node", (node) => {
  console.log(node.type + " created!");
});

core.on("connect-node", (source, dest, output, input) => {

});

var ctx = new AudioContext();

var osc = ctx.createOscillator();
var gain = ctx.createGain();

Build

Run gulp, as ./build/web-audio-instrumentation.js is created. If using source, requires 6to5 transformation.

Testing

Because phantomjs does not have AudioContext, run ./test/index.html in a browser. Hooray.

License

MIT License, Copyright (c) 2015 Jordan Santell