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

ts-arg

v1.0.3

Published

Decorator based argument parsing for typescript

Downloads

25

Readme

TS-Arg

Tool for making decorator based command line argument parsers. More info here

Installation

To use this tool you need to have "experimentalDecorators": true, "emitDecoratorMetadata": true, either in your tsconfig.json or your command line parameters.

Node.js CI

Usage

Add the @Arg decorator to the class you want to use for your CLI.

Example

See a full example in ./example

import {Arg, configure} from "ts-arg";

class MyOptions {
  
   @Arg('do you want it to be chatty')
   verbose:boolean;

   @Arg({short:'T', description:'What is your T'})
   tbone:string;

   @Arg("A number of things");
   count:number;

}

const opts = configure(new MyOptions);


Configuration

If it doesn't quite do what you want checkout the possible options.

     
    long?: string
    short?: string,
    description?: string,
    required?: boolean,
    default?: boolean,
    type?: 'Boolean' | 'String' | 'Number' | 'Int' | 'JSON' | '[]' | any,
    converter?: Converter,
    itemType?: 'Boolean' | 'String' | 'Number' | 'Int' | 'JSON' | any,

Application Style

Sometimes storing the parameters is desired, by labeling your class with the @Config decorator, a few things happen.

  • All commands are prefixed with the "argPrefix" value which defaults to the "prefix" value which itself defaults to className.
  • ENV parameters are enabled allowing ENV properties to be read with the correct prefix. Similar to the argPerfix the envPrefix defaults to the prefix and then to the class name.
  • A configuration file is looked for, by default a JSON file (parser is specfiable). The rcFile variable is defaulted to the .${prefix}. value.
  • A property named packagePrefix which defaults to prefix is read from the current project's package.json and attempts to set the current project.

Example:

#!/usr/bin/env node

import {configure, Config, Arg} from 'ts-arg';

@Config("myapp")
class MyOptions {
  @Arg("verbosity on/off")
  verbose:boolean;

  @Arg({description:"Paths to look for", default:true})
  paths:string[]

  @Arg()
  name:string;
 
}
console.table(configure(new MyOption));

Then options can be provided via cli:

 $ ./bin/myapp.js --myapp-name=stuff -v ./path/to/thing.

or they can be combined with ENV

 $ MY_APP_VERSBOSE=1 ./bin/myapp.js --myapp-name=stuff ./path/to/thing.

and it could be combined with package.json


{
"name": "my-super-app",
"myapp": {
    "name": "stuff"
  }
}

Or a dot file .myapprc

{
   "paths": ["./src","./test"],
 "verbose": true,
}