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 🙏

© 2024 – Pkg Stats / Ryan Hefner

allen

v0.1.7

Published

Utilities for the Web Audio API

Downloads

34

Readme

allen

Build Status

allen is a collection of utilities for the Web Audio API. As of right now, mostly type checking different objects to determine what kind of type of node an object is, but if you find yourself reusing the same methods when developing with the Web Audio API, please add them!

Installation

Methods

getAudioContext()

Creates and returns an available AudioContext for the environment. If this method was called previously, or an AudioContext was set via setAudioContext(), then the same instance will be returned.

setAudioContext( context )

Sets the AudioContext to be returned from getAudioContext().

isAudioContext( node )

Returns true if node is an AudioContext; false otherwise.

isAudioSource( node )

Returns true if node inherits from an AudioSourceNode, like BufferSourceNode, MediaElementAudioSourceNode, MediaStreamAudioSourceNode or OscillatorNode; false otherwise.

isAudioDestination( node )

Returns true if node is an AudioDestinationNode; false otherwise.

isAudioNode( node )

Returns true if node inherits from AudioNode; false otherwise.

isRegularAudioNode( node )

Returns true if node inherits from AudioNode, and is not a source or destination node; false otherwise.

isAudioParam( param )

Returns true if param inherits from AudioParam; false otherwise.

Example

  var
    ctx = allen.getAudioContext(),
    src = ctx.createMediaElementSource( new Audio() ),
    gain = ctx.createGainNode();

  allen.isAudioNode( gain );  // true
  allen.isAudioNode( src );   // true
  allen.isAudioSource( src ); // true
  allen.isAudioSource( gain ); // false
  allen.isAudioParam( gain.gain ); // true

Development

You must have grunt installed globally -- build src and specs and run tests with grunt, or fire off the watcher with grunt watch to build and test changes.

Run tests with grunt mocha. In test/mocks/mockContext.coffee, there is a mock AudioContext object for running tests headlessly -- tests should pass in PhantomJS, as well as browsers.