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

node-respond

v0.0.3

Published

node-respond is an auto-responding Async CLI/CMD wrapper for NodeJS with a syntax based on

Downloads

20

Readme


Respond


node-respond is an auto-responding Async CLI/CMD wrapper for NodeJS with a syntax based on node-suppose by jprichardson (https://github.com/jprichardson/node-suppose).

Why?

After searching around for a super simple way to format a HDD in NodeJS I settled on using nodes child_proccess, but found responding to questions from the CLI an absolute nightmare of spaghetti, and so this was born!

Installation

npm install respond

It's really that easy!

Usage

Note: you can set these in any order you please.

Initiate the funtion: var respond = require('respond');

Set responses: respond.on('what to listen for', 'what to respond with') NOTE: they don't have to be in order!

Set debug: respond.debug(function(msg){ /*Handle message data*/ }) Debug reports all strings to any functions you set to it.

Set error handlers: respond.error(function(errMsg){ /*Handle Error*/ })

Set end handlers: respond.end(function(exitCode){ /*Handle End*/ })

Example

    var respond = require('respond');
    
    respond('npm', ['init'])
    .on(/name\: \([\w|\-]+\)[\s]*/, 'awesome_package')
    .on('version: (0.0.0) ', '0.0.1')
    .on('description: ',"It's an awesome package man!")
    .on('entry point: (index.js) ',"")
    .on('test command: ','npm test')
    .on('git repository: ', "")
    .on('keywords: ', 'awesome, cool')
    .on('author: ', 'Shane Gadsby')
    .on('license: (BSD) ', 'MIT')
    .on('ok? (yes) ', 'yes')
    .error(function(err){
        console.log(err.message);
    })
    .end(function(code){
        console.log('Exit code: ', code)
    })

License

(MIT License)

Copyright 2013, Shane Gadsby