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

@volter/dawproject

v0.5.157

Published

A piece of music as React elements named for DAWproject's own model (Project, Transport, Track, Channel, Device, Clip, Note, Marker), and the renderer that mounts one into a plain graph.

Readme

@volter/dawproject

A piece of music as a React component. The elements are DAWproject's (the open interchange format Bitwig and PreSonus publish): Project, Transport, Track, Channel, Send, Device, Clip, Note, Marker, Points, Point. A reconciler (render.ts, the shape of @pixi/react) mounts the component into a plain graph, and readPiece (piece.ts) reads the graph as a piece. Nothing in a piece imports anything but this package and its own modules.

<Track name="Flute">
  <Channel volume={-3} pan={0.15}>
    <Device plugin="soundfont" params={{ bank: BANK, program: 73 }} />
    <Send to="Hall" level={-14} />
  </Channel>
  <Clip at="1" bars={8}>
    <Note at="1:1" pitch="F#5" dur="h" vel={0.6} />
    <Note at="1:3" pitch="E5" dur="q" artic="legato" />
  </Clip>
</Track>

Written units (notation.ts): at is an absolute bar:beat, pitch a note name, dur a note value (w h q 8 16 32, dots, t for triplets). A <Clip> takes at and bars; the transport takes tempo and meter.

perform(piece) (perform.ts) is the one performance both the editor's preview and the export play: the tempo map (<Points target="tempo">, beats to seconds), articulations, controller lanes sampled into events, and the humanize device's seeded drift.

Apache-2.0. A piece carries this package when it ships.