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

tiny-parse-argv

v2.4.0

Published

A tiny function for parsing process.argv, a modern rewrite of a sensible subset of minimist.

Downloads

101,320

Readme

Tiny Parse Argv

A tiny function for parsing process.argv, a modern rewrite of a sensible subset of minimist.

Features

The following features are provided:

  • Built-in TypeScript types, and pretty clean and understandable code.
  • Single/multiple implicit/explicit shorthand flags: -f, -f some, -f 123, -f123, -abc, -abc 123, -abc123, -f some -f other.
  • Single/multiple implicit/explicit longhand flags: --foo, --foo some, --foo 123, --foo=123, --foo=some, --foo some --foo other.
  • Explicitly negated flags are false by default: --no-foo, --no-bar.
  • Eager flags consume multiple consecutive values: -f one two three, --foo one two three.
  • Arguments: ./app.sh with some list of arguments.
  • Values that would be interpreted as numbers if they were JavaScript are coerced to numbers automatically.
  • Flags that could lead to prototype pollution issues are safely ignored.
  • options.boolean: the value for the listed flags will always be coerced to a boolean.
  • options.string: the value for the listed flags will always be coerced to a string.
  • options.eager: the listed flags are considered to be eager, and will consume multiple consecutive non-flag values.
  • options.variadic: the listed flags are considered to be variadic, and their value, if present, will always be an array.
  • options.required: the listed flags are considered to be required, if some are missing options.onMissing will be called.
  • options.alias: if any aliased flag is assigned then all the aliases for it will be assigned too, automatically.
  • options.default: an object containing default values, which will be used if not overridded by the argv array.
  • options.onInvalid: a function that will be called if any of the provided flags have an invalid value, e.g. a boolean value for a string flag.
  • options.onMissing: a function that will be called if any of the required flags is missing. If a default value is provided for a flag it won't be considered as missing.
  • options.onUnknown: a function that will be called if any of the flags are unknown, i.e. not listed as either a boolean, a string, or an alias. If a default value is provided for a flag it won't be considered as unknown.
  • --: a special flag that stops parsing, everything after it will be copied, untouched, into the -- property of the return object.

Differences with minimist

The following differences exist compared to minimist:

  • option['--'] set to false is not supported, it's as if it's always set to true.
  • option.boolean set to true is not supported, you should always explicitly list all your supported boolean flags instead.
  • option.boolean set to a single string is not supported, always provide an array of flags instead.
  • option.string set to a single string is not supported, always provide an array of flags instead.
  • option.alias mapping to a single string is not supported, always provide an array of aliases instead.
  • option.stopEarly is not supported, it's as if it's always set to false.
  • Dotted flags are not supported, so their paths will not be expanded, you can use path-prop's unflat function for that.

Other than that it should work pretty much identically, since we are basically using the same tests.

Install

npm install --save tiny-parse-argv

Usage

import parseArgv from 'tiny-parse-argv';

parseArgv ([ '-f', '--foo', 'some', 'argument', '--', '--app-flag' ]);
// => { f: true, foo: 'some', _: ['argument'], '--': ['--app-flag'] }

License

MIT © Fabio Spampinato