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

schema-api

v0.2.3

Published

Serves up a JSON definition of a REST API. Enables self documenting services.

Downloads

8

Readme

schema-api

Serves up a JSON definition of a REST API. Enables self documenting services. Validates data against a JSON schema using tv4

Examples


var schemaAPI = require('schema-api')({
    nickname: 'PetService',
    validation: true
});

var app=express();
//validate the data returned from the database against the 'Cat' model using tv4
app.get('/cat.json', loadDatafromDB(), schemaAPI.validate('Cat'),handleErr);

The API schema will be served at /schema and /schema/PetService. The second url means that the Swagger-UI will display the nickname clearly.(https://github.com/wordnik/swagger-ui) This is useful if you are developing a set of micro services which may be deployed on different servers and domains. Each service can serve up a definition of its own API and this will work cross-domain. In production the API schema is not served and the Access-Control-Allow-Origin header is not set.

Options

nickname the name of the service shown by Swagger-UI and the also the final part of the url. schema the path to the schema which defaults to apiSchema.json in the same directory as the main module. validation indicates that you will use tv4 JSON validation. The models will be loaded from your schema file at startup.

Release History

|Version|Date|Description| |:--:|:--:|:--| |v0.2.3|2020-02-12| Debug dependency upgrade to address security vulnerability | |v0.2.2|2014-09-04| Debug logging | |v0.2.0|2014-08-22| TV4 JSON validation | |v0.1.2|2014-05-07| Add Options request for Swagger UI in CORS situation | |v0.1.1|2014-04-30| Access-Control-Allow-Headers | |v0.1.0|2014-04-29| Initial Version|

License

(The MIT License)