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

cli-bespoke

v0.2.0

Published

Parse and validate commandlines. Simple, well-typed and customizable.

Downloads

2

Readme

cli-bespoke

Parse and validate commandlines. Simple, well-typed and customizable.

No dependencies.

Usage

To parse any commandline, use parse() (or parseLazy()) and pass Converter functions for each option.

type Converter<Input, Output> = (value: Input, sendError: ErrorSender) => Output;

The return type is determined by which Converter you pass.
There are several built-in Converters, but you can also pass user-defined ones.

Example

import {
  parse,
  flag,
  first,
  converters as cv,
  converterFactories as cvf,
} from "cli-bespoke";

const args = parse({
  // Arguments to parse.
  args: process.argv.slice(2),

  // Specify all options and their `Converter` functions.
  convert: {
    // Error if either undefined, zero or multiple values.
    _: cv.justOne,

    // No values. Parsed as boolean.
    help: flag,

    // Error if multiple values.
    outfile: cv.optionalOne,

    // Split strings, accepting undefined.
    strs: cvf.optional(cvf.split(",")),

    // A complex example including user-defined converter.
    nums: first(cvf.zeroOrMore(cv.int)).then(cvf.map((n) => n + 1)),
  },

  // Option names and their aliases (not required).
  alias: {
    // -h will be parsed as --help
    help: "h",
  },
});

The result will be typed as follows:

const args: {
  _: string;
  help: boolean;
  outfile: string | undefined;
  strs: string[] | undefined;
  nums: number[]
}

Details about convert:

  • Underscore _ is for parameters that do not belong to any options.
  • Use flag for options that do not receive values.
  • All values are readonly string[] | undefined before converting.
  • Namespace converters provides built-in Converters.
  • Namespace converterFactories provieds functions that produces Converters.
  • You can also use any user-defined converter function.
  • Use first()/then() for chaining multiple Converters.

Config

You can replace any field of config.

import { config } from "cli-bespoke";

config.onError = (err) => {
  console.error(err);
  process.exit(1);
};