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

args-command-parser

v1.2.5

Published

Nodejs minimal opinionated command-line argument parser

Downloads

2,473

Readme

args-command-parser

Nodejs minimal opinionated command-line argument parser.

GitHub Build Status Coverage Status Deno Node.js

Installation

npm install args-command-parser

Usage

Assume that we have created JavaScript version of git and execute it like below:

node git.js commit -m "some message" --amend -abc value --between 1 10

Lets first import the parser from args-command-parser:

Node.js

const { parser } = require('args-command-parser');

ES6

import argsCommandParser from 'args-command-parser';

const { parser } = argsCommandParser;

Deno

import { parser } from 'https://deno.land/x/args_command_parser/mod.js';

now lets call the parser and grab the arguments:

const argv = parser().data;

The value of the argv after the running the code above will be:

{
  commands: [ 'commit' ],
  shortSwitches: { m: [ 'some message' ], a: [], b: [], c: [ 'value' ] },
  longSwitches: { amend: [], between: [ '1', '10' ] }
}

args-command-parser by default parse process.argv.slice(2) but you can pass any array of strings to it.

More Details

args-command-parser is an opinionated command-line parser. The idea is that the commands are in the format below:

node <file.js> [command1 [command2 [...]]] [switches]

Command

Commands are the first arguments showing up. These are names without - or --. As soon as a switch is seen, the sequence of commands is considered finished.

Switch

Switches can be in short or long format.

Short Switch

Short Switches are prefixed with - followed by one or more single-character switch. If more than one character is specified, each character is considered a Short Switch. Short Switches can be followed by zero to any number of values.

Long Switch

Long Switches are prefixed with -- followed by the switch name. Long Switches can be followed by zero to any number of values.

License

MIT