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

swagger-cli-client

v0.1.12

Published

Generates a command-line interface for any Swagger Specification

Downloads

8

Readme

Swagger CLI Client

Generates a command-line interface for any Swagger Specification so you can do things like:

Example usage

Usage

This intended to be embedded within a wrapper application which can provide it the schema object (which is generated using fetch-swagger-schema). For example, here's the petstore-cli file:

#!/usr/bin/env node

var swaggerCli = require('../'),
  schema = require('./petstore-schema.json');

swaggerCli(schema);

To create a cli app for your schema, just require your schema instead of the petstore schema.

Auth lookup strategy

By default the cli will first use the --auth param (if defined), then it'll use the <appname>_AUTH (e.g., PETSTORECLI_AUTH) env variable (if defined), and finally a yaml/json file called .<app-name> (e.g. ~/.petstore-cli which may contain "auth: MY_TOKEN").

Overriding the base path

You can override your api base path via the same lookup strategy as auth keys, this is useful for testing and development. Pass in --basePathOverride <path> or defined a <app-name>_BASE_PATH or a basePath key-value pair in the .<app-name> config file.