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

@synthlet/impulse

v0.2.0

Published

Impulse generator audio worklet

Readme

@synthlet/impulse

A single-sample impulse on every trigger, as an audio worklet

Part of Synthlet.

One parameter, one job: on each rising edge of trigger it writes a single sample of 1 and is silent everywhere else. A gate turned into an event — the excitation for a resonator, a click track, or the ping that starts a @synthlet/karplus-strong string.

Install

npm i @synthlet/impulse

Or npm i synthlet for every module at once.

Usage

import { registerImpulseWorklet, Impulse } from "@synthlet/impulse";

const ac = new AudioContext();
await registerImpulseWorklet(ac);

const impulse = Impulse(ac, { trigger: clock.gate });
impulse.connect(ac.destination);

Parameters

| Param | Default | Range | Rate | Meaning | | --------- | ------- | ----- | ------ | ----------------------------- | | trigger | 0 | 0 … 1 | a-rate | Rising edge emits one impulse |

trigger is a-rate, and here that changes what is detectable: at k-rate the processor read one sample per block, so a pulse that rose and fell inside a render quantum produced no impulse at all — not a late one, none. It now fires, and a trigger arriving mid-block is seen in that block.

The impulse is still written at index 0 of the block. That is deliberate: the spec samples a k-rate AudioParam at the first sample-frame of each quantum, so an impulse written anywhere else would be invisible to a native AudioParam a caller left k-rate. What stopped being quantised is the detection, not the placement — so two rising edges inside one block still yield one impulse.

License

MIT © danigb