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

@linterhub/usage-parser

v1.1.0

Published

Simple parser for usage page in CLI

Downloads

4

Readme

@linterhub/usage-parser travis semantic npm github

Simple parser for usage page in CLI

Table of Contents

Background

There are a lot of CLI with different usage doc, distributed in different ways. This repository contains a proposal to unified format for arguments of various CLI. Under the hood, the main idea is pretty similar to docopt approach.

More details in doс or at the catalog page

Install

npm install @linterhub/usage-parser

GitHub

All releases and the source code are available for download at GitHub Releases.

Usage

Parse help doc and output result to console:

JavaScript

const usageParser = require('@linterhub/usage-parser');

const usage = new UsageParser('Help doc from CLI');
console.log(usage.parse());
import UsageParser from '@linterhub/usage-parser';

const usage = new UsageParser('Help doc from CLI');
console.log(usage.parse());

CLI

Usage: bin [options] <binary>

Parse help page specifying binary as argument or content as option

Options:
  -V, --version      output the version number
  -d, --docs <docs>  The help page content (pass without <binary> argument)
  -f, --file <file>  Path to a file with CLI docs
  -h, --help         output usage information

Examples:
  $ usage-parser mocha   // Parser runs help command for `mocha` and parse output
  $ usage-parser eslint  // Parser runs help command for `eslint` and parse output
  $ usage-parser --file "usage-file.txt"
  $ usage-parser --docs "usage text"

Contribute

You may contribute in several ways like requesting new features, adding tests, fixing bugs, improving documentation or examples. Please check our contributing guidelines.

License

MIT