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

command-box

v0.1.0

Published

A console widget. This differs from [echo-chamber](http://github.com/jaz303/echo-chamber) by using an `<input>` tag instead of handling user input manually.

Readme

command-box

A console widget. This differs from echo-chamber by using an <input> tag instead of handling user input manually.

Usage

var CommandBox = require('command-box');

// #console should be a div element
var widget = new CommandBox(document.querySelector('#console'), {
    
    // example of an async evaluator
    evaluate: function(command, console) {
        console.notReady(); // hide input box

        // now evaluate the submitted command
        doWork(function(result) {

            // print output to console
            console.print(result);

            // and set up the console for the next command
            console.newCommand(true);
            console.focus();
        
        });

    },

    prompt: function(console) {
        return { text: '> ' }
    },

    // submitted commands should be echoed to the output
    echo: true
});

// tell the widget to prepare itself for new input by clearing any existing
// input and setting a new prompt. the true paramater indicates that the console
// should also be 'made ready' meaning that the input box will be revealed.
widget.newCommand(true);
widget.focus();

Default styles are in default.css; you can substitute the base command-box class for whatever you wish.

Copyright & License

© 2014 Jason Frame [ @jaz303 / [email protected] ]

Released under the ISC license.