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

hermes-server

v0.3.0

Published

End point aggregation server. Useful for providing a single url for all of your micro service endpoints.

Downloads

4

Readme

Hermes

End point aggregation server. useful for providing a single url for all of your micro service endpoints.

Usage

npm install --save hermes-server

'use strict';

const Hermes = require('hermes-server');
const routeSupplier = new Hermes.FileSystemRouteSupplier({
  filePath: './node_modules/hermes-server/routes.example.json'
});
const hermes = new Hermes.Server(routeSupplier, 3000);

hermes.on('listening', (port) => {
  console.log(`Hermes started on port ${port}`);
});

hermes.on('proxy', (method, path, target) => {
  console.log(`${method} ${path} => ${target}`);
});

Route Suppliers

In order to know where to proxy traffic, Hermes needs to be provided with a set of routes. This is achieved by instantiating a RouteSupplier.

Default Route Suppliers

Hermes comes with two route suppliers, Hermes.SimpleRouteSupplier and Hermes.FileSystemRouteSupplier

SimpleRouteSupplier

Provides routes based on an object passed on instantiation

const routeSupplier = new Hermes.SimpleRouteSupplier({
  routeData: [{
    'name': 'Test route',
    'methods': ['GET'],
    'pattern': '/test',
    'target': {
      'protocol': 'http',
      'host': 'example.com',
      'pathname': '/'
    }
  }]
});
routeSupplier.getRoutes().then(routes => { console.log(routes) });

FileSystemRouteSupplier

Reads routes from a JSON file, the path of which is passed to the constructor

const routeSupplier = new Hermes.FileSystemRouteSupplier({
  filePath: './node_modules/hermes-server/routes.example.json'
});
routeSupplier.getRoutes().then(routes => { console.log(routes) });

Custom Route Suppliers

To allow custom generation/retrieval of routes, it is possible to create your own RouteSupplier

const Q = require('q');
const Route = require('Hermes').Route;

class MyRouteSupplier extends Hermes.RouteSupplier {
  constructor(options) {
    super(options);
  }

  getRoutes() {
    return Q.promise((resolve) => {
      fetchRoutesFromSomeService().then((routes) => {
          resolve(routes.map(data => new Route(data)));
      });
    });
  }
}

Route Format

Routes should be defined as below

[{
  // A unique identifier for the route
  "id": "Test route",
  // Which methods should be proxied
  "methods": ["GET", "POST", "PUT", "DELETE"],
  // The hermes path that should be requested in order to have it proxied to
  // the target. Supports RegEx's
  // IE
  // http://your-hermes-instance.com/test => http://example.com/
  // http://your-hermes-instance.com/test/thing => http://example.com/thing
  "pattern": "/test(.*)",
  // The target that the request should be proxied to. Accepts all values that
  // url.format accepts https://nodejs.org/api/url.html#url_url_format_urlobj
  "target": {
    "protocol": "http",
    "host": "example.com",
    "pathname": "/$1"
  }
}]