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 🙏

© 2024 – Pkg Stats / Ryan Hefner

mdlr

v0.0.3

Published

a react component library for building declarative synthesizer instruments and systems

Downloads

6

Readme

mdlr Build Status npm package

⚠️ mdlr is just a lil bb library right now ⚠️
⚠️ ~please contribute if it interests you~ ⚠️

table of contents

intent

mdlr is an abstraction of synthesis via the web audio API in the form of composable React components.

While it draws inspiration from react-music, its goals differ. If react-music could be considered most equivalent to a synthesizer workstation, mdlr would be best compared to Max (perhaps its BEAP library in particular), or modular synthesizers. Nonetheless, mdlr draws inspiration from other javascript libraries and web audio API abstractions such as react-music and i_dropped_my_phone_the_screen_cracked

mdlr is not concerned with implementing methods of control like sequencers, MIDI input, or basic musical time structures. In fact, mdlr doesn't even implement musical pitch (since this is easily derived by other utilities like note-to-frequency) in favor of frequency. Decisions about control, timing, temperament, etc. are better made in the context of mdlr's use.

installation

via npm:

npm install --save mdlr

or via yarn:

yarn add mdlr

usage

import { AudioContext, Output, Oscillator, Modulation } from 'mdlr';

const ToneGenerator = ({ freq }) => (
  <AudioContext>
    <Output>
      <Oscillator frequency={freq} waveform="sawtooth">
        <Modulation parameter="frequency">
          <Oscillator frequency={30} />
        </Modulation>
        <Modulation parameter="amplitude">
          <Oscillator frequency={2} />
        </Modulation>
      </Oscillator>
    </Output>
  </AudioContext>
);

reference

⚠️ documentation for components needed here! ⚠️

development

prerequisites

Node.js >= v4 and Yarn must be installed.

installation

  • Running yarn install in the components's root directory will install everything you need for development.

demo development server

  • yarn start will run a development server with the component's demo app at http://localhost:3000 with hot module reloading.

formatting

  • yarn lint will run linter on scripts.
  • yarn pretty will prettify scripts.

running tests

  • yarn test will run the tests once.

  • yarn test:coverage will run the tests and produce a coverage report in coverage/.

  • yarn test:watch will run the tests on every change.

building

  • yarn build will build the component for publishing to npm and also bundle the demo app.

  • yarn clean will delete built resources.