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

sendak-usage

v0.0.10

Published

A command-line parser/usage generator wrapping nopt

Downloads

13,078

Readme

sendak-usage

It became clear after writing the bulk of Sendak's command-line components that a common "header" accompanied each task that included the command-line options, their long- and short- arguments, defaults, and descriptions, from which nopt-usage would generate a "usage" statement and nopt would do the actual parsedown into a hash.

But this was big and sprawling and when @konklone said to me that he uses minimist, I was peeved because I wanted to be able to switch and realised I had coded myself into this nopt and nopt-usage-shaped corner where I could not just forklift in minimist if I wanted to.

Accordingly I wrote this tiny package to abstract away the command-line parser I am using with usage stuff into a single hash so that I am not dependent on the vagaries of other packages (ahem, looking at you, nopt-usage…) that may or may not be actually maintained.

It is published here primarily so that Sendak can require it, but you should feel comfortable that it will continue to be maintained for at least as long as Sendak is if it is useful to you.

Usage

From the original issue:

var parsed = require( 'sendak-usage' ).parse( {
  // This is a full argument declaration
  //
  'help': {
    'long-args': [ 'help', 'halp' ],
    'description': 'sets the helpful bit',
    'short-args': [ 'h' ],
    'default': false
    'type': [ Boolean ]
  },
  // But all you need to do is specify the type of argument you want.
  //
  'long-arg-name': { 'type': [ Boolean ] }
} );

Author

@avriette, jane.avriette@gsa.gov