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

consistency

v1.1.0

Published

API versioning plugin for hapi.js

Downloads

232

Readme

npm version Build Status

Consistency

A hapi.js plugin for versioning your API. Borne out of this talk: http://www.slideshare.net/shakefon/hapidays-2014

Installation

npm install consistency

Register plugin with your hapi application, provide the option(s) required for version detection.

server.register({
  register: require('consistency'),
  options: {
    uriParam: 'apiVersion',
    acceptNamespace: 'consistencyExample',
    customHeaderKey: 'api-version'
  }
}, function (err) {
  if (err) console.log('Consistency plugin failed to load');

});

or, via Glue and manifest:

var manifest = {
  connections: [...],
  plugins: {
    consistency: {
      uriParam: 'apiVersion',
      acceptNamespace: 'consistencyExample',
      customHeaderKey: 'api-version'
    }
  }
};

Glue.compose(manifest, function (err, server) {
  ...
});

Versionize your Routes

Array of handlers

server.route({
  id: 'array',
  method: 'GET',
  path: '/array',
  handler: {
    versioned: [
      function(request, reply) {
        reply({
          version: '1.0'
        });
      },
      function(request, reply) {
        reply({
          version: '2.0'
        });
      }
    ]
  }
});

Object of handlers

server.route({
    id: 'object',
    method: 'GET',
    path: '/object',
    handler: {
      versioned: {
        'v1.0': function(request, reply) {
          reply({
            version: '1.0'
          });
        },

        'v2.0': function(request, reply) {
          reply({
            version: '2.0'
          });
        },

        'v1.5': function(request, reply) {
          reply({
            version: '1.5'
          });
        }
      }
    }
});

Version Matching

A version can be provided with or without the v prefix and can also be provided using the latest keyword which will use the latest versioned endpoint.

Matching of version handlers is cached to remove redundent checks based on the route method and route path.

If an endpoint has not changed in a specific version of the api, we can omit it and the matcher will use the version that is closest to the one request. for example if in version 2 we didn't update the users endpoint a request would return version 1

If you provide the version in shorthand (v1, 1) it will return greatest version available for that api version. for example given the versions 1, 1.2, 1.5 providing 1 will return 1.5.