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

get-arguments

v1.0.2

Published

Returns the object with CLI command, arguments and values passed by the user.

Downloads

13

Readme

Description

get-arguments package gets the process.argv and returns object with command and arguments passed by the user in the command line.

Quick start

npm install get-arguments

Considering that there is "bin" : { "myapp" : "./cli.js" } in your package.json file:

If there is a limited number of valid commands, use:
//cli.js
const args = require('get-arguments');

const commandName = "myapp"; //your CLI command name
const validCommands = ['init','config','update','list','build']; //your allowed commands

args(commandName,validCommands,function(argsObject){
  if(argsObject===null) return;
  //argsObject returns null if:
    //the incorrect command was typed by the user 
    //the arguments syntax typed by the user was incorrect
  //do your magic here
  //use argsObject.command
  //use argsObject.args
});

If the user types incorrect command, the following message in the command line is printed:

Usage: myapp <command>
where <command> is one of:
   init,
   config,
   update,
   list,
   build
If the user is allowed to type any command, use:
//cli.js
const args = require('get-arguments');

args(function(argsObject){
  if(argsObject===null) return;
  //argsObject returns null if:
    //the arguments syntax typed by the user was incorrect
  //do your magic here
  //use argsObject.command
  //use argsObject.args
});

CLI arguments syntax:

Acceptable:

The user can pass a command with:

  • no arguments
  • only argument value(s)
  • argument pair(s) of name and value(s)
> myapp command
> myapp command valA valB valC
> myapp command -p val
> myapp command --param val
> myapp command -p valueA valueB valueC --force
> myapp command --name John --age 25 --title "New Project"

Unacceptable:

> myapp command valA valB --param
> myapp command valA valB -p

If the user types incorrect arguments syntax, the following message in the command line is printed:

Invalid arguments.

Behaviour

> myapp init

{
  command:'init',
  args:[]
}

> myapp build a b c

{
  command:'build',
  args:['a','b','c']
}

> myapp config --get name title age

{
  command:'config',
  args:{
    '--get':['name','title','age']
  }
}

> myapp config --get name title age --set title "New Title"

{
  command:'config',
  args:{
    '--get':['name','title','age'],
    '--set':['title','New Title']
  }
}

> myapp init --path ./project --async -f

{
  command:'init',
  args:{
    '--path':['./project'],
    '--async':[],
    '-f':[]
  }
}