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

foparsearguments

v0.0.17

Published

Function to parse command line arguments for Node.js programs

Downloads

18

Readme

foParseArguments

Parse Node.js arguments library.

Getting Started

  1. Install foParseArguments via NPM.

npm install foparsearguments

Optionally: rename foparsearguments to foParseArguments: npm is unable to handle the complexity of uppercase characters in a module name. Node.js on Windows does not have this problem, so renaming the folder is not required for you to use the module.

  1. Require foParseArguments in your project.

var foParseArguments=require("foParseArguments");

  1. Parse arguments using foParseArguments.
var oArguments = foParseArguments({
  "dfxTypesConverters": { 
    "myType": function (sValue) {
      if (!isvalid(sValue) throw new Error("must be a valid xxx");
      return processed(sValue);
    }, // define a type
    ...
  },
  "adxParameters": [ 
    {
      "sName": "first parameter",
      "sTypeDescription": "string",
      "sHelpText": "This will be shown when you run the script with -?",
      "xDefaultValue": "first"
    },
    {
      "sName": "second parameter",
      "sTypeDescription": "int",
      "sHelpText": "This will be shown when you run the script with -?",
      "xDefaultValue": 2
    },
    ...
  ],
  "dxSwitches": {
    "switch-name": {
      "sHelpText": "This will be shown when you run the script with -?",
    },
    ...
  ],
  "dxOptions": {
    "option-name": {
      "sTypeDescription": "myType", // option must be of mytype.
      "sHelpText": "This will be shown when you run the script with -?",
      "xDefaultValue": 2
    },
    ...
  }
});
  1. Used parsed arguments in your script
var uSomeNumber = oArguments.dxOptions["some-number"];
var sSomeString = oArguments.axParameters[0];
var bSomeBoolean = oArguments.dbSwitches["some-boolean"];

Notes

Alpha release

This has not been extensively tested and the API will most likely change in the future.


License

This code is licensed under CC0 v1.0 Universal.