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

@thisismanta/pessimist

v2.0.0

Published

```ts import { parseArguments } from '@thisismanta/pessimist'

Downloads

68,144

Readme

import { parseArguments } from '@thisismanta/pessimist'

const args = parseArguments(
    process.argv.slice(2), 
    {
        dryRun: false,
        count: 0,
        outputFileName: '',
        exclude: [],
    }
)
node myfile file1 file2--output-file-name=file3 

The above command yields args of the following type.

{
    // From the field-value arguments
    outputFileName: 'file3',

    // From the defaults
    dryRun: false,
    count: 0,
    exclude: [],

    // From the positional arguments
    '0': 'file1', 
    '1': 'file2',
    length: 2,
}

Unknown field rejection

The below commands exit with non-zero code as somethingElse is not defined in the default object (the second parameter of parseArguments function).

node myfile --something-else

Therefore it is important to have all the possible field-value arguments defined in the default object.

Auto camel case conversion

The below commands yield the same output as dry-run is transformed into a camel case.

node myfile --dryRun
node myfile --dry-run

Field aliases

The below commands yield the same output as -d is an alias of --dryRun which is defined in the extra options.

parseArguments(
    process.argv.slice(2), 
    {
        dryRun: false,
    },
    {
        aliases: [['d', 'dryRun'], ...],
    }
)
node myfile --dryRun
node myfile -d

False-like Boolean recognition

The below commands yield the same output.

node myfile --dryRun=false
node myfile --dryRun=False
node myfile --dryRun=FALSE
node myfile --dryRun=n
node myfile --dryRun=no
node myfile --dryRun=0

Negation and clearance

The below commands yield dryRun === false as no prefix negates the Boolean value.

node myfile --noDryRun
node myfile --no-dry-run

The below commands yield outputFileName === '' as no prefix sets the value to an empty string.

node myfile --noOutputFileName
node myfile --no-output-file-name

The below commands yield input == [] as no prefix sets the value to an empty array.

node myfile --noExclude
node myfile --no-exclude

Duplicate-free guarantee

The below commands yield input: ['file2', 'file1'] as it does not keep duplicate values.

node myfile --exclude=file1 --exclude=file2 --exclude=file1

Mutual exclusive fields

The below command throws an error as both fields are defined as mutually exclusive in the extra options.

parseArguments(
    process.argv.slice(2), 
    {
        dryRun: false,
        confirmed: true,
    },
    {
        exclusives: [['dryRun', 'confirmed'], ...],
    }
)
node myfile --dryRun --confirmed