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

supersonic-scsynth-core

v0.96.0

Published

The WebAssembly synth and AudioWorklet of SuperSonic, a scsynth-compatible synth powered by Clockwork

Readme

supersonic-scsynth-core

The SuperSonic engine for the browser: SuperCollider's scsynth synthesis engine compiled to WebAssembly, running on the clockwork substrate inside an AudioWorklet. It takes OSC in, renders audio out, and answers the scsynth command set. The client that talks to it is supersonic-scsynth, which loads this package from wherever you tell it to: a CDN, or a path on your own server.

Contents

  • wasm/clockwork-scsynth.wasm - the engine
  • wasm/clockwork_midi_bg.wasm, wasm/clockwork_gamepad_bg.wasm - the Web MIDI and gamepad modules, fetched only when the client turns them on (midi: true, gamepad: true)
  • workers/clockwork_audio_worklet.js - the AudioWorklet processor that runs the engine on the audio thread
  • index.js - CDN URLs for this release of the package (CORE_CDN, WASM_CDN, WORKLET_CDN)

Usage

The client needs to be told where this package is, with coreBaseURL. From a CDN:

import { SuperSonic } from 'https://unpkg.com/supersonic-scsynth@latest/dist/supersonic.js';

const supersonic = new SuperSonic({
  baseURL: 'https://unpkg.com/supersonic-scsynth@latest/dist/',
  coreBaseURL: 'https://unpkg.com/supersonic-scsynth-core@latest/'
});

Without coreBaseURL the client looks for the engine under baseURL, and the client package ships no wasm, so init() fails.

Self-Hosting

To host the core yourself, point coreBaseURL at your copy, alongside the client's own files:

import { SuperSonic } from 'supersonic-scsynth';

const supersonic = new SuperSonic({
  workerBaseURL: '/path/to/supersonic-scsynth/dist/workers/',
  coreBaseURL: '/path/to/supersonic-scsynth-core/'
});

Installation

npm install supersonic-scsynth-core

Then serve the wasm/ directory and workers/clockwork_audio_worklet.js from your static file server.

License

AGPL-3.0-or-later. The synthesis code is GPL-3.0-or-later, forked from SuperCollider's scsynth by James McCartney and the SuperCollider community; it runs on clockwork (AGPL-3.0-or-later), and the combined work is AGPL.

Related Packages