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

@strudel/osc

v1.3.2

Published

OSC messaging for strudel

Downloads

382

Readme

@strudel/osc

OSC output for strudel patterns! Currently only tested with super collider / super dirt.

Usage

Assuming you have node.js installed, you can run the osc bridge server via:

npx @strudel/osc

You should see something like:

osc client running on port 57120
osc server running on port 57121
websocket server running on port 8080

--port

By default it will use port 57120 for the osc client, which is what superdirt uses. You can change it via the --port option:

npx @strudel/osc --port 7771 # classic dirt

--debug

To log all incoming osc messages, add the --debug flag:

npx @strudel/osc --debug

Usage in Strudel

To test it in strudel, you have can use all(osc) to send all events through osc:

$: s("bd*4")

all(osc)

open in repl

You can read more about how to use Superdirt with Strudel in the tutorial.