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

@nodeguy/cli

v0.2.3

Published

command line interface helper functions

Downloads

7

Readme

These are simple tools for writing a Command Line Interface (CLI) program.

Features

Arguments Parser

Yes, I wrote Yet Another Arguments Parser, even though there are already plenty (including one called Yargs!). I wanted one with a simpler API that accepts standard data structures for defining options instead having to call methods.

Usage Example

"use strict";

const { cli } = require(`@nodeguy/cli`);

cli(
  {
    answer: [`The Answer to the Great Question`],
  },
  ({ answer }) => {
    console.log(`The answer is ${answer}.`);
  }
);
$ node test.js --help
Usage: test.js [options]

Options:
  --answer                   The Answer to the Great Question
  --help                     print usage instructions

$ node test.js --answer=42
The answer is 42.

cli(optionsSpecification, callback) -> (async)

optionsSpecification is an object in the following format:

{
  optionName1: [`description of option 1`, `default value1`]
  optionName2: [`description of option 2`, `default value2`],
  ...
}

The default values are optional and may be omitted.

callback is a function that will be called with an object of parsed options, .e.g.,

{
  optionName1: `default value1`
}

For more usage examples see test/index.js.

Shell

Run a shell script in the middle of a JavaScript program:

"use strict";

const { shell } = require(`@nodeguy/cli`);

;(async () => {
  await shell(`
# List the files in the root directory.
cd /
ls
`);
});

Copyright

Copyright 2018 David Braun

Licensed under the Apache License, Version 2.0 (the "License"); you may not use these files except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.