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

rii

v1.0.2

Published

CLI command runner

Readme

rii

Install

npm install --global rii

Command Line Usage

rii <command> --some-flag

About

rii is a mechanism to consume scripts that contain functions that are called by name as <command>. For instance if you were to run rii <command> on the command line.

Any file with a .cmd.js extension will run by executing rii.

Example

my_directory/script.cmd.js

function thing1(ctx, world){
    //To run this function:
    //rii thing1
    console.log('I am thing one.');
}

function thing2(ctx, world){
    //To run this function:
    //rii thing2
    console.log('I am thing two.');
}

function throwError(){
    //To run this function:
    //rii throw-error
    //This error will print to the console.
    throw new Error('an error');
}

Change to my_directory run rii thing1, and the console prints I am thing one..

Run rii "thing1 thing2", and the console will print:

I am thing one.
I am thing two.

init

If you have an init.cmd.js file in the directory you run rii this init.cmd.js will be run first. If you have an init() function defined in init.cmd.js that function will be ran before all others.

Arguments

Each function you define will receive two arguments ctx (first parameter), and world (second parameter).

ctx is a regular object where you can set properties at your leasure. All properties/values set on ctx will be shared.

world is an object that gives you access to values, and operation(s).

world

The world parameter will look something like this:

World {
  cwd: '/path/to/my_project',
  argv: [
       '/usr/bin/nodejs',
       '/path/to/rii' ],
  filename: 'script1.cmd.js',
  extend(object){
      //Passing object here extends `ctx`
  }
}

To do

  • Better documentation
  • Show coverage
  • Add sub-directory runner

Support acorn which is used in rii source.