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 🙏

© 2025 – Pkg Stats / Ryan Hefner

choraljs

v1.0.5

Published

SATB choral voicing library compatible with TonalJS

Downloads

12

Readme

choraljs

A TypeScript library for generating SATB (Soprano, Alto, Tenor, Bass) choral voicings using TonalJS.


Installation

npm install choraljs @tonaljs/tonal @tonaljs/progression deepmerge

Usage

import { Progression, SATB, ChordSpec } from 'choraljs';

// Create a progression in C major
const prog = new Progression({ key: 'C', scale: 'major' });

// Chain voicings
prog
  .voiceChord('I')      // I chord in C major
  .voiceChord('vi')     // vi chord
  .voiceChord('IV');    // IV chord

console.log(prog.results.voicings);

// Check legal next moves
console.log(prog.legalMoves().map(m => m.chord));

// Validate a chord without adding
console.log(prog.validateChord('V'));  // true or false

// Modulate to G major via pivot
prog.modulate('G').voiceChord('V').voiceChord('I');

// Directly insert a custom SATB voicing
const custom: SATB = { S: 'E4', A: 'C4', T: 'G3', B: 'E3' };
prog.addDirect(custom, 'custom');

// Batch build
const batch = Progression.fromArray(['I','IV','V','I'], { key: 'F', scale: 'major' });
console.log(batch.results.voicings);

API

Progression

  • constructor(options?: Partial)

    • options.key: starting key (default 'C')
    • options.scale: scale type (default 'major')
    • options.voicing: 'close' | 'open' (default 'close')
  • voiceChord(spec: ChordSpec): this Voice a chord (Roman numeral, chord name, or { notes: string[] }).

  • legalMoves(): Array<{ chord: DiatonicNumeral; voicing: SATB }> Get all next-step diatonic Roman numerals that avoid parallels/spacing errors.

  • validateChord(spec: ChordSpec): boolean Check if a chord can be voiced legally at the current progression point.

  • modulate(newKey: string, newScale?: string): this Pivot-mid progression modulation by detecting a common chord.

  • addDirect(satb: SATB, label?: string): this Directly append an existing SATB voicing (throws if voice-leading errors).

  • results

    • voicings: array of { chord: string; key: string; voicing: SATB }
    • errors: array of { chord: string; key: string; message: string }
  • static fromArray(arr: ChordSpec[], opts?: Partial<Context>): Progression Build a progression from an array of chord specs in one call.

Contributing

  1. Clone the repo
  2. npm install
  3. npm run build and npm test
  4. Submit PRs for new features or bug fixes.