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

reapack

v1.1.11

Published

Command-line tool for ReaPack index file generation

Downloads

19

Readme

Command-line (Node.js module) for ReaPack index file generation

This is an index generator and release manager for a ReaPack collection (REAPER effects, themes, etc.) hosted on a static site (e.g. GitHub Pages, or your own web-server). It is written in Node (JavaScript).

How it works

The state is stored in reapack.json, and this is used to generate the index.xml used by ReaPack. (Do not modify index.xml, your changes will be overwritten.)

Each release copies the applicable files to a new release folder, with a JSON file (reapack-version.json) describing that release. To create index.xml, the directory is scanned for reapack-version.json files.

How to install

npm install -g reapack

If a global install (-g) doesn't work, then you can do a local install, and instead of just running reapack, run node node_modules/reapack.

How to use it

The command-line attempts to be intuitive (use --help on any command to get more information), but here are some examples to get started:

View the index and list all packages:

> reapack index

Geraint's JSFX
--------------
README: README.md
links:
           website:     https://geraintluff.github.io/jsfx/
packages:
        Bad Connection (effect in "Distortion")
        Dual Distortion (effect in "Distortion")
        Spectrum Matcher (effect in "Utility")

View a package:

> reapack package "Bad Connection"
Bad Connection
--------------
type:           effect
category:       Distortion
version:        1.0.1
files:
        Bad Connection.jsfx
        ui-lib.jsfx-inc
links:
        screenshot: Bad Connection.png

Add/remove files:

> reapack package "Bad Connection" --add "some-file.jsfx" --remove "other-file.jsfx"

Simulate a ReaPack install (useful when developing your effects):

> reapack install C:\Users\Geraint\AppData\Roaming\REAPER

TODO

There are some missing features (e.g. a command to add links, remove/rename packages), which at the moment are only possible by editing reapack.json by hand.