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

oa3-md

v1.0.6

Published

Converts Open API or Swagger specification from YAML or JSON-file into a compact and easy to read Markdown Report

Downloads

411

Readme

Openapi 3 to Markdown Report

wcs badgenpm version

Converts Openapi 3 specification from YAML- or JSON-file into a compact and easy to read Markdown Report.

Features

  • Command line with single parameter
  • Consumes Swagger 2 and Openapi 3
  • Consumes YAML and JSON
  • Compact Markdown output in cheat sheet format
  • Configurable

Usage

npm install oa3-md -g

oamd apispec.yaml apispec.md

First parameter is open api spec file name. Default extension is .json if omitted. Second parameter is the output file name. It is the source file name if omitted.

API

const oamd      = require('oa3-md');
const fileIn    = 'user.json';
const fileOut   = 'user.md';
const options   = {
    "advertising": false
}
oamd.oaFileToMdFile( fileIn, fileOut, options );

The package exports:

function oaFileToMdString (oaFile, options = {})

Read file oaFile and return markdown as string.

function oaFileToMdFile (oaFile, mdFile, options = {})

Read file oaFile and write output to file mdFile.

options

Options is content of file config.json

{
    "use_example":              false,
    "default_ext_in":           ".json",
    "default_ext_out":          ".md",
    "advertising":              true,
    "logo":                     true,
    "txt": {
        "pathTable":            "## Path Table",
        "thMethod":             "Method",
        "thPath":               "Path",
        "thDesc":               "Description",
        "pathDetails":          "## Path Details",
        "requestBody":          "##### ⇨ Request Body",
        "requestParams":        "##### ↣ Parameter",
        "response":             "##### ⇦ Response"
    }
}

References

Example Output


User API Spec

Version 1.0.0


This is a oa3-md test specification

Path Table

| Method | Path | Description | | --- | --- | --- | --- | | [GET](# Get user list) | /user | Get user list | | [POST](# Add a new user) | /user | Add a new user | | [GET](# Get user by id) | /user/{id} | Get user by id |

Path Details

Get user list

GET /user

⇦ Response
[{
    "id": <integer>  // user id
    "name": <string>  // user name
}, ..]

Add a new user

POST /user

⇨ Request Body
{
  "name": <string>  // user name
}
⇦ Response
{
  "id": <integer>  // user id
  "name": <string>  // user name
}

Get user by id

GET /user/{id}

↣ Parameter
  • id in path
    user id (required)
⇦ Response
{
  "id": <integer>  // user id
  "name": <string>  // user name
}