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

clargs

v0.1.0

Published

An easy way to gather user input for your scripts.

Downloads

1

Readme

clargs Build Status

I found myself writing a lot of CLI apps that used argify to convert command-line args into values that I could use in code. This worked well, but I was constantly having to crack open the script source to remind myself which args a particular script expected.

I like being prompted to provide arguments, but sometimes I want to just 'up-arrow+enter' a script instead.

To address this, I wrote clargs to combine the functionality of argify with the super-awesome inquirer module. The idea is that you can provide args at the command-line, and get prompted for the ones you forget

Use

Using clargs is simple. Because it has the potential to accept user input, I have it return a promise so that you can integrate it cleanly into your app.

clargs accepts an array of Inquirer question objects. The name property of each question correlates to the -- argument specified at run-time. For example:

/**
 * $ node ./myscript.js --foo=bar
 */

 // myscript.js
'use strict';

var clargs = require('clargs');

var questions = [{
  type: 'input',
  name: 'foo', // --foo=bar
  message: 'foo'
}, {
  type: 'confirm',
  name: 'baz', // there was no --baz so this question is asked
  message: 'baz?',
  default: true
}];

clargs(questions)
	.then(function(args) {
		console.log('Args:', args);
    /**
     * { foo: 'bar', baz: true }
     */
	});

Versions

  • 0.1.0 - Removed q dependency, updated deps
  • 0.0.1 - Initial commit