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

bos-openapi-doc-server

v1.0.0

Published

BlueOak Server Middleware to serve OpenAPI (Swagger) docs

Downloads

3

Readme

BlueOak Server Middleware to serve OpenAPI (Swagger) docs

Using BlueOak Server, started with nodemon, and this project, you can author OpenAPI (swagger) specs using your editor, and have them rendered and served to your browser in ReDoc.

This BlueOak Server middleware uses ReDoc to serve the OpenAPI (Swagger) specs defined in a BlueOak Server project (template).

installation

In a BlueOak Server project (template):

$ npm i --save bos-openapi-doc-server

configuration

Since this is BlueOak Server middleware, it won't be used unless you configure it to be used.

In your server config (e.g. config/default.json):

  1. add "bos-openapi-doc-server" to your list of "middleware"
  2. customize what and where the docs get served in the swagger.docPublish object

list of config options affecting this functionality

  • swagger.docPublish.context (optional): where the ReDoc-rendered specs should be served from
    • default: "/docs"
  • swagger.docPublish.redocUrl (optional): provides the ability to override where to get ReDoc from
  • swagger.docPublish.templatePath (optional): facilitates using your own custom ReDoc template
    • the template may use whiskers syntax to have the follow variables added:
      • title: the title for the spec given in the OpenAPI definition
      • version: the version of the spec given in the OpenAPI definition
      • specObject: a JavaScript Object representing the specification
      • specUrl: the URL where BOS is serving the JSON representation of the OpenAPI definition
      • redocSrc: the location of the source file for ReDoc, if it is available locally
      • redocUrl: the location of the ReDoc source if it is to be retrieved over the network
      • redocOptions: a JavaScript Object into which the swagger.docPublish.redocOptions object will be passed
    • the default template at templates/openapi-doc.html is a good starting point for customization
  • swagger.docPublish.redocOptions (optional): an object with any customizations to ReDocs behavior following the descriptions of the <redoc> tag attributes in camelCase

sample default.json config

{
  "express": {
    "port": "3003",
    "middleware": [
      "bos-openapi-doc-server",
      "bodyParser"
    ]
  },
  "cluster": {
    "maxWorkers": 1
  },
  "bodyParser": {
    "json": {}
  },
  "swagger": {
    "serve": true,
    "useLocalhost": true,
    "refCompiler": {
      "api-v1": {
        "baseSpecFile": "api-v1.yaml",
        "refDirs": [
          "v1"
        ]
      }
    },
    "docPublish": {
      "context": "/docs",
      "templatePath": "lib/templates/my-spec-docs.html",
      "redocOptions": {
        "scrollYOffset": 50,
        "suppressWarnings": true,
        "lazyRendering": true,
        "requiredPropsFirst": true
      }
    }
  }
}

That config will cause the spec defined in swagger/api-v1.yaml to be served at localhost:3003/docs/${api-path}, using the custom ReDoc template in your project at lib/templates/my-spec-docs.html.