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

hapi-microservice

v2.1.4

Published

Quickly setup a Hapi 17 Server

Downloads

6

Readme

HapiMicroService

npm version

A micro service utility class that encapsulates all the necessary logic to quickly setup and run a Hapi 17 Server.

Installation

Install HapiMicroService as a dependency of your project

npm i -S hapi-microservice

Setup

Require HapiMicroService and create a new instance. Give the instance a unique name, pass in a Hapi server configuration object, a Bunyan logger configuration object, a lag probe interval that's passed through to the Logger instance, and a health check path that defaults to '/health'.

  // ...
  const MicroService = require('hapi-microservice'); 
  const microService = new MicroService('MyAwesomeServer', {
    server: {
      // hapi 17 server config object
    },
    log: {
      // bunyan logger config 
    },
    routePrefix: '/api', // prefix all routes
    lagProbeInterval: 250 // refresh rate for measuring event loop lag (in ms)
  });
  // ... 
  microService.start();

Adding routes and handling Hapi responses

HapiMicroService provides a method on the base class for adding routes. and standardizing responses and response formatting. Refer to the Hapi route config option docs for more information on object formatting.

Hapi17 doesn't seem to provide a way in the server configuration object to prefix all routes. Because of this implementors of HapiMicroService should always register routes through MicroServices helper and not directly to this.server.

Due to addRoutes being an asynchronous function (server.register is also async) we must handle the returned Promise.

  // ...
 
  const MicroService = require('hapi-microservice') 
  
  const microService = new MicroService('MyAwesomeServer', {
    server: {
      port: 3000
    },
    routePrefix: '/api'
  });
  
  async function init() {
    const routes = [{
      method: 'GET',
      path: '/path/to/resource',
      // note that there is no reply() function in Hapi17, you either use `responseToolkit` or return a value
      handler: async (request, responseToolkit) => {
        let result;
        try {
          result = await myAwesomePromiseReturningService();
        } catch(err) {
          MicroService.replyHandler(err, null, responseToolkit);
          return;
        }
        MicroService.replyHandler(null, result, responseToolkit);
      } 
    }];
    await microService.addRoutes(routes);
  }
  
  // NOTE:  that all promises must be handled in Node
  init()
    .catch(err => {
      // handle err
    });
  // ...