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

owncli

v0.0.4

Published

command line runner

Readme

owncli

nodejs command line utility

getting started

setup new npm project sample cli

mkdir samplecli
cd samplecli
npm init
npm install owncli --save

create your cli startup file

touch index.js

var config = {
    tasks: __dirname + '/tasks',
    mainCommand : 'sample'
};

require('owncli').init(config, function(err, cli){
  cli.execute();
});

create your first tasks

mkdir tasks
cd tasks

touch test.js

module.exports = {
    commands: {
        one: {
            description: 'do one thing',
            execute: require('./test-one'),
            options: {
                significance: {abbr: 's', description: 'significance of version',required: true}
            }
        }
        two: {
            description: 'do two things',
            execute: require('./test-two'),
            options: {
                verbose: {abbr: 'v', description: 'set verbosity'},
                save: {abbr: 's', description: 'save the settings', required: true},
                env: {abbr: 'e', description: 'set environment', required: true, values: ['dev', 'prod']}
            }
        }
    }
};

touch test-one.js

var runner = require('owncli').runner;

module.exports = function(options){

    runner(options)

        .echo("Here we go!")
        .exec("cat index.js")
        .get('version').from('package.json').as('oldVersion')
        .semver('oldVersion').as('newVersion')
        .set('version').in('package.json').to('newVersion')
        .echo("Done!")

        .go(function (err, results) {
            console.log('options', options);
            console.log(err || results || '');
        });

};

touch test-two.js

module.exports = function(options){
	console.log("three");
};

try your cli

node index //=> outputs help

node index test //=> outputs help for the test command

node index test one -s patch //call test-one command

debug

WINDOWS: SET DEBUG=owncli & node index.js
*nix: DEBUG=owncli & node index.js