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

hapda

v0.4.0

Published

A bridge for serverless Hapi

Downloads

22

Readme

Hapda

Define Hapi route handlers for serverless, lambda (req, res) endpoints.

Features

  • Full access to the Hapi API and ecosystem
  • Uses shot.inject rather than running a real Hapi instance, meaning no extra TCP overhead, no extra HTTP overhead
  • Clean and concise, doesn't get in your way
  • Leverage entire existing Hapi ecosystem, validation, plugins, caching, architecture
  • Build battle-tested serverless handlers instead of hacking together raw http endpoints

What is it?

If like me, you like the idea of serverless but dislike the lambda / node http / express / polka API format, and prefer Hapi's routing, this allows you to do the following:

const { hapda } = require('hapda')

module.exports = hapda({
  method: 'GET',
  path: '/foo/bar',
  handler: () => {
    return { baz: 'qux' }
  }
})

and then publish your serverless function as normal.

How do I use plugins?

You can access the entire Hapi instance by passing a method which is given the Hapi instance as a parameter.

const myMethod = async server => {
  server.plugins(...) // or routes, handlers, anything you can do with Hapi at all.
}

module.exports = hapda(myRoute, myMethod)

An example with some caching and auth

The following example does two things:

  • Sets up authentication in basic mode (with a super secure password ;))
  • Sets up a cached server-function whose value is cached for 15 seconds
const validate = async (request, username, password, h) => {
  const isValid = username === 'admin' && password === 'admin123'
  return { isValid, credentials: { id: 123, username } }
}

async function setupServer (server) {
  await server.register(require('@hapi/basic'))
  server.auth.strategy('simple', 'basic', { validate })
  server.auth.default('simple')

  server.method(
    'time',
    () => new Date(),
    {
      cache: {
        expiresIn: 15000,
        generateTimeout: 100
      }
    }
  )
}

const route = {
  method: 'PUT',
  path: '/foo/bar',
  handler: () => {
    return { lastCachedTime: server.methods.time() }
  }
}

module.exports = hapda(route, setupServer)

Troubleshooting

Caching / Plugin X doesn't work.

For reasons of speed, Hapda doesn't call initialize() on bootstrap. Normally, this function would be called by server.start() but because we don't call that, or bind to a port or listen for HTTP connections, it never gets called. If you find that you need to call initialize() to finalize plugin registration or start caching, you can do so using the server setup method:

async function setupServer (server) {
  await server.register(someComplexPlugin)
  await server.initialize()
}

const route = {
  method: 'GET',
  path: '/foo/bar',
  handler: () => {
    return { foo: 'bar' }
  }
}

module.exports = hapda(route, setupServer)