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

flag-parse

v0.1.0

Published

a node tool for parse command flag

Downloads

39

Readme

Flag-parse

A node tool for parse command flag

function

we provide a tool to parse the command flag in node env, if the field has double horizontal line --name=roadhub, it is a full name ,else if the field has a single horizontal line only,it is a shortcut name -n=roadhub,it 's value will be map to it's full name's value

> node -f --name=roadhub --age=12 index.js

in index.js

var flag = require("flag-parse").default

/**
 * default: a default value when process.argv has no this flag
 * type: is data type for this field , one of `string` , `number` and `bool`
 * usage: is usage for this field ,it will be print when you call flag.printHelp
 * shortcut: this is optional field , it is a abbreviation for this field
 */

let flags = flag.parse({
    name:{default: "", type: "string", usage:"user's name",shortcut:"n"},
    fork:{default: true, type: "bool", usage:"is fork",shortcut:"f"},
})
flag.printHelp("usage: `git <command>`, follow flag is useable:", "thank you to use git")

you can get this argument in flags, if you forget to config a field , it will be push to rest by the original order

console.log(flags) // {fork: true, name: "roadhub",}
console.log(flag.rest) //["--age=12", "index.js"]
flag.printHelp("usage: `git <command> <flag>`, follow flag is useable:", "thank you to use git")
/**
 *  usage: `git <command> <flag>`, follow flag is useable:
 *
 *          -name,-n    user's name
 *          -fork,-f    is fork
 *
 *  thank you to use git
 */

thanks