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

arguments-parser

v3.2.1

Published

A node arguments parser

Downloads

13

Readme

arguments-parser

NPM

npm version

A simple and configurable node arguments parser.

Usage

const args = require('arguments-parser')();
console.log(args); // output: { 'p': 2300 }

running: node index.js -p 2300

Number and booleans are parsed.

Since v2.0.0 the output object has no keys middle dashs

Configuration

  1. Create a folder named config.
  2. Create a file named arguments-parser.json inside config folder.
  3. Create an array of available arguments strings inside arguments-parser.json file.
  4. Call arguments-parser with configuration object.

Configuration object

const args = require('arguments-parser')({
    explicit: true, // use configuration file: default false
    keepAsArray: true, // true: keep all values as arrays or false: if only one value to the item, the item config will be this single value (not an array) : default false
    onlyParamsArray: true // returns an array of received params : default false
    offset: 2 // offset for removing default params of node : default 2
})

If explicit mode is set to true and no configuration file exists in config folder, a warning message will appear into console. If onlyParamsArray is set to true, explicit and keepAsArray will be ignored

Example: arguments-parser.json

['--styles', '--routing', ['--port', '-p']];

** Since v2.0.0 no differences between using one or two middle dash, no differences between --port and --p **

['styles', 'routing', ['port', 'p']];

Note that the third config element is an array of strings, it can be used to assign two or more flags to same configuration. This configuration for arguments-parser will produce this json when we call node with:

node index.js --skipgit --port 4200 -p 3200 --styles=scss

{
    "skipgit": true,
    "styles": "scss",
    "port": 4200
}

node index.js --skipgit --p 3200 --port 4200 --styles=scss

{
    "skipgit": true,
    "styles": "scss",
    "port": 4200
}

Before v2.0.0 the properties of the object has the exact name of the properties configuration

As you can see, the first element of the array (for multiple flags to same configuration) is the key of the result object, and has more height than other flags (for same configuration, in this case "-p" vs "--port" is sended in de node command, the result will be builded with "port" value)

Other considerations

  • In the previous examples the --style flag value has an equal before the value itself, you can define your values with '=' or with a whitespace.
  • If no value has passed into a parameter, by default equals true

Remove no config info message

Since v2.0.0 No message will appear if not set the explicit mode to true.

If you want to use arguments-parser without config, to remove the warning message create the configuration file with no content. [v2.0.0 - Set explicit mode to false or leave it without configuration]