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

arge

v1.5.2

Published

A simple utility to parse command line arguments and flags

Downloads

17

Readme

Arge

A tiny package to parse CLI flags and arguments into an object.

Installation

yarn add arge

# or
npm i arge

Usage

const { arge } = require('arge')

// or
import { arge } from 'arge'

Then:

const args = arge(process.argv)

This will return arguments parsed from process.argv like this:

node app.js --dry-run --mode=development --test=false --retries=100

...into an object similar to below:

{
  "dryRun": true,
  "mode": "development",
  "test": false,
  "retries": 100
}

Typescript

For type safety, arge will accept a generic for typing the resulting object.

Example

const { foo, bar } = arge(process.argv)

In the above scenario, foo and bar will report the following:

Property 'foo' does not exist on type 'unknown'

Property 'bar' does not exist on type 'unknown'

To address this, we can apply a generic:

interface Args {
  foo: string
  bar: number
}

const { foo, bar } = arge<Args>(process.argv)

API

arge(flags, options?)

Returns a key-value pairs object of flags

flags

Type: string[]

options

Type: object | undefined

isArgv

Type: boolean

Default: true

By default, the arge function assumes that you have passed process.argv. It does this because:

The first element will be process.execPath.

The second element will be the path to the JavaScript file being executed

https://nodejs.org/docs/latest/api/process.html#processargv

This package will omit those two items from the output.

If you wanted to pass an arbitrary array of flags that don't come from process.argv, you can set this option to false.

For example

const flags = [
  '--dry-run',
  '--mode=development',
  '--test=false',
  '--retries=100',
]

const args = arge(flags, { isArgv: false })

This would then output:

{
  "dryRun": true,
  "mode": "development",
  "test": false,
  "retries": 100
}
camelCaseKeys

Type: boolean

Default: true

This converts hyphen separated keys into camel case. To prevent this behaviour, you can set this value to false.

const flags = ['--dry-run']

const args = arge(flags, { camelCaseKeys: false })

This would then output:

{
  "dry-run": true
}