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

interplay

v1.1.0

Published

Modular UI controls library designed for both debugging and performance environments, with a focus on simplicity and providing multiple interaction methods.

Readme

interplay

Modular UI controls library designed for both debugging and performance environments, with a focus on simplicity and providing multiple interaction methods.

Developing a new Input Node

JavaScript API

domElement = InputNode(node)

Each Input Node is exposed as a function which takes a node object and returns a DOM element to be attached to the interplay input list. Interfacing with interplay is done through the node object that's passed through to you.

node.input.manual = true|false

Should be set to true if manual input is supported, e.g. buttons, sliders, and any other directly manipulable UI elements.

module.exports = function (node) {
  node.input.manual = true
  // ...
}

node.input.keyboard = true|false

Should be set to true if keyboard input is supported, e.g. it can be triggered using key presses without directly interacting with the node.

module.exports = function (node) {
  node.input.keyboard = true
  // ...
}

node.input.midi = true|false

Should be set to true if MIDI input is supported.

module.exports = function (node) {
  node.input.midi = true
  // ...
}

node.value

Change node.value to set the node's output value.

node.on('change', changed)

Calls the changed function whenever the Node's value is changed.

node.on('init', init)

Calls the init function when the Node is added to interplay. Should be used to set up event listeners, load assets, etc.

Note that init may be fired more than once if the node is added/removed multiple times.

node.on('stop', stop)

Calls the stop function when the Node is removed from interplay. Should be used to clean up any allocated resources created when firing the init function.

Note that stop may be fired more than once if the node is added/removed multiple times.

Required CSS Classes

.interplay-manual

Should wrap the manual input mode of the Input Node.

.interplay-keyboard

Should wrap the keyboard input mode of the Input Node.

.interplay-midi

Should wrap the MIDI input mode of the Input Node.