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

@tanisjam/lime-renderer-tone

v0.1.0

Published

LIME browser renderer using Tone.js. The only place Tone.js is allowed.

Readme

@tanisjam/lime-renderer-tone

Browser renderer for LIME built on Tone.js — the only LIME package allowed to depend on Tone. Maps @tanisjam/lime-core's tick-based symbolic events onto Tone.Transport for real-time playback.

This package requires a browser (Web Audio) environment to actually produce sound; its exports resolve and type-check under Node, but running it needs a browser or a Web Audio polyfill.

Install

npm install @tanisjam/lime-renderer-tone tone

tone is a peer dependency — install it yourself so your app shares one Tone instance (and one AudioContext/Transport) between LIME and any other Tone-based code you run. LIME targets tone@^15.

Usage

import { createLime } from "@tanisjam/lime-core";
import { createToneRenderer } from "@tanisjam/lime-renderer-tone";
import { ambientMinimal } from "@tanisjam/lime-styles";

const renderer = createToneRenderer({ instrumentation: ambientMinimal.instrumentation });

const music = createLime({
  seed: "forest-level-12",
  style: ambientMinimal,
  renderer,
  initialState: { energy: 0.2, tension: 0.1, valence: 0.65, tempo: 76 },
});

// Call from a user gesture — Web Audio requires it.
await music.start();

API

  • createToneRenderer(options?: ToneRendererOptions): ToneRenderer — build a MusicRenderer for createLime({ renderer }).
    • options.instrumentation — per-voice mix config.
    • options.instruments — override per-voice InstrumentFactorys (e.g. a Tone.Sampler-based instrument with your own samples); voices without an override use the built-in self-contained palette.
  • Built-in instrument factories and genre palettes (DEFAULT_INSTRUMENT_FACTORIES, ROCK_INSTRUMENTS, POP_INSTRUMENTS, JAZZ_INSTRUMENTS, METAL_INSTRUMENTS, and more) are exported for reuse or as a reference when writing your own.

See the root README and ARCHITECTURE.md for how this fits into the rest of LIME.