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

beat-scheduler

v1.0.0

Published

A clock for audio

Readme

Beat-scheduler

An event-based audio clock with variable bpm and swing for use in the browser

Install

npm install beat-scheduler --save

Basic Use

var ac = new window.AudioContext()
  , ee = require('nee')()
  , opts = { bpm: 135, swing: 0.1, lookahead: 0.2, ee: ee }
  , clock = require('beat-scheduler')(ac, opts)

clock.on('next-tick', function (beat) {
  // do something notable...
})

clock.play()

Configuration Options

  • opts.bpm integer - beats per minute
  • opts.swing float - a value between 0 and 1 representing the amount of "swing" in the beat
  • opts.lookahead float - number of seconds (typically a fraction thereof) to look ahead for not events

Methods

  • clock.play() start the clock
  • clock.stop() stop the clock
  • clock.changeBpm(bpm) set the bpm to a number
  • clock.changeSwing(swing) change the swing to a float between 0 and 1
  • clock.on(event, handler) register handler as a callback when event is fired; handler will receive a beat object

Beat Objects

  • beat.now float - audio context time at which the tick was published
  • beat.beatLength float - the total length of this beat (adjusted for swing)
  • beat.lookahead float - audio context time to look ahead to; users will typically use this to schedule events for the future
  • beat.lastBeat float - audio context time at which the previous beat occurred
  • beat.nextBeat float - audio context time at which the next beat will occur

Events

Beat-scheduler emits only one event type:

  1. next-tick events fire on a request animation frame loop, passing a beat object

If you hand in an event emitter with on and emit methods, beat-scheduler can also respond to events:

  1. schedule-play will be handled by clock.play
  2. schedule.stop will be handled by clock.stop
  3. bpm-change will be handled by clock.changeBpm
  4. swing-change will be handled by clock.changeSwing