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 🙏

© 2026 – Pkg Stats / Ryan Hefner

args-json

v1.4.3

Published

Zero-dependency descriptively typed command-line argument parser

Readme

args-json

Zero-dependency descriptively typed command-line argument parser

Contents: parseArgs · Args · isOn / isOff / isExplicitlyOff

parseArgs

String input

import { parseArgs } from "args-json";

const args = parseArgs(
  "--config=./config.json -v 1.0.0 -d \"lorem ipsum\" -i -n=0 --test-value abc --debug",
  {
    v: "version",
    d: "description",
  }
);
// args = {
//   config: "./config.json",
//   version: "1.0.0",
//   description: "lorem ipsum",
//   i: true,
//   n: 0,
//   testValue: "abc",
//   debug: true,
// };

Note that keys and values can be separated from each other either with a space or an equals sign, and the value can be either quoted or not. These variants are equivalent. Also, keys are converted to camelCase (like --test-valuetestValue in the example above).

The second parameter is optional. It is a way to rename argument keys in the output. In the example above, -d and -v in the input string are renamed to description and version in the output object.

Other examples:

const args = parseArgs("--config ./configs/default.json --debug");
// { config: "./configs/default.json", debug: true }

if (args.debug) console.log(args.config);

The first line is also equivalent to:

const args = parseArgs("--config \"./configs/default.json\" --debug");

or

const args = parseArgs("--config=./configs/default.json --debug");

or

const args = parseArgs("--config=\"./configs/default.json\" --debug");

String array input

const args = parseArgs(["--config", "./configs/default.json", "--debug"]);
// { config: "./configs/default.json", debug: true }

if (args.debug) console.log(args.config);

Node process arguments

In a Node environment, parseArgs() without parameters parses the node process arguments.

const args = parseArgs();

is equivalent to

const args = parseArgs(process.argv);

If the process object is unavailable in the current environment, parseArgs() is equivalent to parseArgs([]).

Key mapping

const args = parseArgs("-c ./configs/default.json --debug", { c: "config" });
// { config: "./configs/default.json", debug: true }

if (args.debug) console.log(args.config);

As specified with the second parameter of parseArgs(), -c is mapped to config in the output.

Value parsing

Values are JSON.parsed if they are parsable.

const args = parseArgs("-d \"{\"x\":10}\" -i 0 -n=3 -c ./config.json");
// { d: { x: 10 }, i: 0, n: 3, c: "./config.json" }

Unkeyed values

Values that aren't preceded by a dashed key (like -x or --xxx) are collected in an array under an empty key entry.

const args = parseArgs("unkeyed args --debug -x 0 -y 1");
// { "": ["unkeyed", "args"], debug: true, x: 0, y: 1 }

Descriptive typing

The output type can be descriptively specified, without validation, by providing a generic type to parseArgs<T>().

type CustomShape = {
  level?: number;
  debug?: boolean;
};

const args = parseArgs<CustomShape>("--level=0 --debug");

if (args.debug) console.log(`Level: ${args.level}`);

Args

Use an Args class instance to facilitate access to named command line arguments:

import { Args } from "args-json";

const args = new Args(["--key", "value", "--paths", "./x", "./y"]);

args.hasKey("--key") // true
args.hasKey("--arg") // false
args.getValue("--key") // "value"
args.getValues("--paths") // ["./x", "./y"]

Without an argument array, new Args() is equivalent to new Args(process.argv) (or new Args([]) if the process object is unavailable in the current environment). An Args object initialized without arguments can also be directly imported with import { args } from "args-json";.

isOn / isOff / isExplicitlyOff

Use isOn(x) and isOff(x) to check whether a parameter value is true, 1, "on" or false, 0, "off", null, undefined.

import { parseArgs, isOn, isOff } from "args-json";

// isOn
isOn(parseArgs("--debug").debug) // true
isOn(parseArgs("--debug=1").debug) // true
isOn(parseArgs("--debug=on").debug) // true

isOn(parseArgs("").debug) // false
isOn(parseArgs("--debug=0").debug) // false
isOn(parseArgs("--debug=off").debug) // false

new Args(["--debug"]).isOn("--debug") // true
new Args(["--debug", "1"]).isOn("--debug") // true
new Args(["--debug", "on"]).isOn("--debug") // true

// isOff
isOff(parseArgs("").debug) // true
isOff(parseArgs("--debug=0").debug) // true
isOff(parseArgs("--debug=off").debug) // true

new Args([""]).isOff("--debug") // true
new Args(["--debug", "0"]).isOff("--debug") // true
new Args(["--debug", "off"]).isOff("--debug") // true

Note the difference between isOff(x) and isExplicitlyOff(x): isExplicitlyOff(x) results in true if x is present and it's explicitly a turn-off value, while isOff(x) returns true if x is omitted, too.

import { parseArgs, isOff, isExplicitlyOff } from "args-json";

isOff(parseArgs("--debug=off").debug) // true
isOff(parseArgs("--debug=0").debug) // true
isOff(parseArgs("").debug) // true

isExplicitlyOff(parseArgs("--debug=off").debug) // true
isExplicitlyOff(parseArgs("--debug=0").debug) // true
isExplicitlyOff(parseArgs("").debug) // false

Use the utility types On and Off (or ExplicitlyOff) to define a switch parameter type:

import { parseArgs, type On, type Off } from "args-json";

type Params = {
  debug?: On | Off;
};

const args = parseArgs<Params>("--debug=on");