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

connect-version

v1.0.4

Published

Multiple Versioned Applications/APIs with Connect

Downloads

9

Readme

connect-version

Multiple Versioned Applications/APIs with Connect

Getting Started

$ npm install connect-version

API

var connectVersion = require('connect-version');

app.use(connectVersion(options));

The connectVersion object is a factory function to create middleware enabling multiple versions of an application to be hosted by a single connect server. The options parameter provides configuration for the factory. It provides a dictionary of supported version numbers and the corresponding middlewares/routers/sub-applications to use when the version is requested.

By default, connect-version uses Content-Type negotiation to determine the correct version number to use for an incoming request.

Example

Varying Application/API version by Content-Type

This example demonstrates using content type negotiation to return a different response body based on what version the client whats to accept. The server lists it's supported versions via the options parameter and will use semantic versioning to find an appropriate match for the client's request.

// server.js
var express = require('express');
var connectVersion = require('connect-version');

var app = express();

var options = {
  versions: {
    '2.0.0-beta.1': require('./routes/2.0.0-beta.1'),
    '1.2.3': require('./routes/1.2.3')
  },
  match: 'Content-Type' // this is the default matcher
};

app.use(connectVersion(options));
// routes/1.2.3/index.js
var express = require('express');
var app = module.exports = express();

// normal routes defintions
app.get('/', function(req, res) {
  res.send('Hello from version 1.2.3!');
});
// routes/2.0.0-beta.1/index.js
var express = require('express');
var app = module.exports = express();

// middleware that only applies to this version of the API
app.use(function(req, res, next) {
  console.log('Woah, this user is on the bleeding edge!');
  next();
});

// normal routes defintions
app.get('/', function(req, res) {
  res.send('Hello from version 2.0.0-beta.1!');
});

Example Request:

GET / HTTP/1.1
Host: example.com
Accept: application/vnd.com.myservice+text;version=1.2.x

Example Response:

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8

Hello from version 1.2.3!