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

@antimatter-audio/antimatter-ui

v14.13.1

Published

React UI component library for Antimatter Audio.

Readme

Antimatter UI

A small library of UI components and styles for Animatter Audio.

Github

File structure

antimatter-plugin-template/
├── Assets // Shared assets between the js and Juce apps.
├── js // The React front end.
├───── node_modules/@antimatter-audio/antimatter-ui // The UI component library <-- You are here.
├── juce // The Juce plugin application.

Getting started

This project is intended to be used as a dependency in the antimatter-plugin-template repository.

To use antimatter-ui within the context of antimatter-plugin-template, follow the setup instructions here.

Development

antimatter-plugin-template contains a demo of all antimatter-ui components.

antimatter-plugin-template is made to bootstrap Juce plugins. The front end application in the js folder can also be viewed in a web browser, so you do not need to worry about running Juce while working on UI components.

To view a demo of these components, follow the instructions for setting up antimatter-plugin-template here

Adding new components

If you build a new component for this library, add the component to the demo in antimatter-plugin-template.

If your new component controls an AudioProcessorValueTreeState paramater in Juce, you will need to handle getting and setting that state in your React component, and you will also need to set up a parameter for that state in the demo Juce app in antimatter-plugin-template.

See core/Buttons/Button.tsx, core/Input/Dropdown.tsx, and core/Input/Slider.tsx for examples of how to get and set Juce's ToggleState, ComboBoxState, and SliderState.

See the main project README file for more information.

Theming

See the main project README file for more information.

Publishing

First, commit all changes in this repo to git:

git add -A

git commit -m "your update message here"

git push

If you are working on your main branch, that's all you need to do.

If you are working on a feature branch, go to github, open a new pull request, and then merge the pull request.

Then, you can switch back to your main branch: git checkout main

And update your local main branch with the changes from github: git pull

When you have gotten everything merged to git, you are ready to publish this project to the npm registry!

First, run:

npm run build

Then, depending on whether your update is a major change, minor change, or a patch, run one of the following: npm version major || npm version minor || npm version patch

Finally, run: npm publish