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

@focme/argv

v3.0.2

Published

node command arguments formater

Downloads

12

Readme

create-argv

a useless node arguments formater

usage

const createArgv = require("@focme/argv")

const argv = createArgv() // a map
const argvObject = argv.object() // an object

createArgv() will return a map object for the options
createArgv().object() will return an object for the options
createArgv().opt() will return an object for the options that every key removed the leading - or --
createArgv().array() will return an entries of the options map

// --config ./webpack/webpack.dev.config

console.log(createArgv())
// Map(1) { "--config" => "./webpack/webpack.dev.config" }

console.log(createArgv().object())
// { "--config": "./webpack/webpack.dev.config" }

console.log(createArgv().opt())
// { "config": "./webpack/webpack.dev.config" }

console.log(createArgv().array())
// [["--config", "./webpack/webpack.dev.config"]]

pipe and commit

pipe

pipe(command, callback, type)

use pipe() function to put a callback into a map for one key in the options
the callback could be an async function

// call this pipe callback while there is a command --key
createArgv().pipe("key", value => { ... }).commit(() => { ... })

// always call this pipe callback whether there is a command --key
// the value will be undefined
createArgv().pipe("key", value => { ... }, "always").commit(() => { ... })

// will not call the pipe callbacks after this pipe if there is a command --key
createArgv().pipe("key", value => { ... }, "break").commit(() => { ... })

commit

use commit() function to run the callbacks in the pipe
after commit() complete the pipe will be cleard

await createArgv().pipe(key, value => {
    ...
}).commit()

as commit is an async function
always should use async before it or use then after it

in the callback of commit will send the keys in createArgv but not in the pipe
return false the commit will stop run pipe callbacks

// -V
await createArgv().pipe("v", value => {
    console.log("version 10.01")
}).commit((keys) => {
    // keys = ["-V"]
    if (keys.length > 0) {
        console.log(`bad option ${key}`) // bad option -V
    }
    // commit will not run the pipe callbacks if keys.length > 0
    return keys.length < 1 
})

dont use the commit callback if dont care about the not matched keys