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

koa-swagger-editor

v1.0.0

Published

A koa middleware, to serve api files and settings for swagger-editor

Downloads

13

Readme

koa-swagger-editor

Build Status

A backend service for swagger-editor, using koa.

Table of Contents

Usage

Installation

Add koa-swagger-editor to your project using npm and --save option:

$ npm install koa-swagger-editor --save
{
  "name": "awesome-package",
  "dependencies": {
    "koa-swagger-editor": "^1.0.0"
  }
}

Download swagger-editor

Download swagger-editor.zip from here

or use the following script in your package.json

{
  "name": "awesome-package",
  "scripts": {
    "download": "if [ ! -d \"./swagger-editor\" ]; wget https://github.com/swagger-api/swagger-editor/releases/download/v2.9.9/swagger-editor.zip; unzip swagger-editor.zip -d swagger-editor; rm swagger-editor.zip; fi"
  },
  "dependencies": {
    "koa-swagger-editor": "^1.0.0"
  }
}

then run

$ npm run download

which will download and extract the dist directory to swagger-editor/ (only if swagger-editor/ does not already exists). In this case your options.statics is <projectRoot>/swagger-editor/dist

Quickstart

'use strict';

const koa = require('koa');
const swagger = require('koa-swagger-editor');

const server = koa()
	.use(swagger({
		statics: __dirname + '../swagger-editor/dist', // path to extracted swagger-editor.zip
		specFile: __dirname + '/simple.api.yml' // where we want to save our api specs
	}))
	.listen(3000);
	
console.log('Listening on 0.0.0.0:3000');

process
	.on('SIGINT', () => server.close())
	.on('SIGTERM', () => server.close());

Now simply head to http://localhost:3000, and start writing your API

API

require('koa-swagger-editor')(options)

will return a koa-mount middleware, which you can use like any other middleware with koa.use()

Options

some options are required, so you cannot miss the options object. Optional options are surrounded by []

options.statics The path to the swagger-editor directory, where index.html is located

options.specFile The file path which is used to read/write our api specs

[options.path='/'] The url mount path, default is '/'

[options.defaults={}] The options object for swagger-editor. Here you can override any settings from swagger-editor/config/defaults.json

[options.defaults.useYamlBackend=true] Right now its hardcoded true and you are not able to change this, because swagger-editor has some problems with loading json into the editor

[options.defaults.useBackendForStorage=true] This is true by default, otherwise i would say you are using this extension without reason

[options.specURL] The URL used by swagger-editor to read/write the specs. Default is the same as in swagger-editor/config/defaults.json:backendEndpoint