npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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




Triple Triangle Synth Thing





NPM js-standard-style

Triple Oscillator Triangle Synthesizer AKA tri-tri AKA TOTS

(an experiment in publishing web audio synths to npm, much like

DEMO: a lil game in which you must show different colors to the camera in order to get it to perform a more pleasing drone.


var context = new (window.AudioContext || window.webkitAudioContext)()
var makeTriTri = require('tri-tri')
var triTri = makeTriTri(context)

makeTriTri returns an object that posses the following methods:

  • keys() => returns list of keys to audioNodes
  • connect(destination) => connect the output nodes to a destination or other nodes
  • start() => calls start() on all the source nodes
  • export() => returns JSON respresentation of the instrument
  • import(data) => loads JSON data, or uses default values if no data is passed.
  • updateNote(noteStr, scale) => sets the synth frequencies to play a major chord in the given note and str. note should look like "E4", etc. Scale can be "major", "minor", "pentMaj", "pentMin", or "blues", and defaults to "major".


// connect yr triTri to the audio context destination, or to other nodes

// => ['root', 'third', 'fifth', 'delay', 'pregain', 'filter', lowFilter', 'distortion', 'volume']
// returns a list of keys to audio nodes, so you can do stuff like triTri.source.type = "square" or whatever. 
// Mostly there for debugging. I guess hopefully they will always be named such that you can guess which type of node they will be....

triTri.start() // begin making noise
triTri.updateNote("C4", "pentMin") // update the root note/scale

var data = triTri.export() => exports the current state of the audio nodes to a json object
triTri.import(data) => resets state of audio nodes from JSON object

Can theoretically use this with