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 🙏

© 2026 – Pkg Stats / Ryan Hefner

swaggerise

v1.0.9

Published

Package to convert joi schema and metadata to swagger json.

Readme

swaggerise

A command-line utility to generate Swagger compatible yaml and json by parsing Router annotations.

Installation

NA

Notes

  1. It can only be run on the root folder of a express-style project. ( It must have a route folder where all router files are present)
  2. The project root folder can contain a schema folder which will be scanned for external object schema. ( Useful for representing objects which are sent in the body of a request. Currently only JOI schema is supported)
  3. A conf file will be generated if not present in the project folder. Users must take care to edit the conf file before generating the swagger yaml.
  4. All route files must export only the router object. Else, it won't be considered as a route file.

Usage

Run the index file on a express project root folder.

express-project-root> node ./path-to-swaggerise/index.js

Router annotations :

  1. @parameters - Reference to external schema file. Syntax is '#/path-to-schema-file'. If more than one schema is exported from the schema file, access it like a regular JSON. Ex. '#/path-to-schema-file.propertyKey'.
  2. @description - Description for this particular endpoint.
  3. @summary - Summary for the particular endpoint.
  4. @operationId - Unique operation id
  5. @produces - Stringified JSON array of response type.
  6. @consumes - Stringified JSON array of api input type.
  7. @responses - Stringified JSON object of possible response codes and description for them.

Module annotations :

  1. @@description - Description for the whole router file/module.
  2. @externalDocDesc - Description for external document for the module.
  3. @externalDocUrl - Url for the external document.

Example

Router annotation :

/**
 * @parameters #/user.js.add  
 * @description Description for this path
 * @summary Summary for this route
 * @operationId Unique operation id
 * @produces ["application/json"]
 * @consumes ["application/json"] 
 * @responses   '{"200":{"description":"successful operation"}}' 
 */

server.post('/add', validation(schema.add), async (req, res, next) => {
    //Endpoint handler.
}

Module annotation :

/**
 * @description hello
 * @externalDocDesc doc
 * @externalDocUrl  http://tis.io/terms/
 */
module.exports = router;

TO-DO

  1. Add support for other external schema types other than Joi.