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

lambda-express-middlewares

v1.0.0

Published

Express like middlewares for AWS lambdas

Downloads

14

Readme

Lambda express middlewares

This package helps you chain AWS lambda functions with an API that is similar to Express middlewares.

The goal of this package is to help you and your team extract any common functionality into new lambda middleware functions. You are then able to order them however you want. The middlewares are executed left to right, the last one will invoke your handler.

This package has no external dependencies, to avoid adding any bloat to your lambda functions.

Examples

Here are some examples for how this package could be used. The middlewares here are obviously just for demo puroposes.

Supercharge your context with extra functionality(like a custom user object):

import { withMiddlewares } from 'lambda-express-middlewares'

const authenticate = async (token) => {
  const user = await authenticaitonService.getUser(token)
  return user
}

// Create a middleware for adding a custom user object to your lambda context.
const authMiddleware = async (event, context, next) => {
  const user = await authenticate()
  const userContext = { ...context, user }
  return await next(event, userContext)
}

// Create a middleware that relies on the user being there, and fetches additional information.
const orderMiddleware = async (event, context, next) => {
  const { user } = context
  const orders = await orderService.getOrders(user.email)
  const orderContext = { ...context, orders }
  return await next(event, orderContext)
}

// Your regular lambda handler.
const apiHandler = async (event, context) => {
  const { user, orders } = context
  // ... your specific logic

  return { statusCode: 200, body: JSON.stringify({ message: 'success' }) }
}

// Export your handler with middlewares.
export const handler = withMiddlewares([authMiddleware, orderMiddleware], apiHandler)

Create a reusable middleware for validating your requests:

import { withMiddlewares } from 'lambda-express-middlewares'

const orderRegex = new RegExp(/^[0-9A-F]{8}-[0-9A-F]{4}-4[0-9A-F]{3}-[89AB][0-9A-F]{3}-[0-9A-F]{12}$/i)

// Your custom middleware, takes in an additional next function, similar to express.
const validateOrderMiddleware = async (event, context, next) => {
  const orderId = event.pathParameters.orderId

  if !(orderRegex.test(orderId)) {
    // Validation failed, you can therefore exit early by returning and not invoking the *next* function.
    return { statusCode: 400, body: JSON.stringify(null) }
  }

  // Validation passed, invoke the handler!
  return await next(event, context)
}

// Your regular lambda handler.
const apiHandler = async (event, context) => {
  // At this point you know that the orderId has been validated
  const orderId = event.pathParameters.orderId
  // ... your specific logic

  return { statusCode: 200, body: JSON.stringify({ message: 'success' }) }
}

// Export your handler with middlewares.
export const handler = withMiddlewares([validateOrderMiddleware], apiHandler)

Your middlewares can wrap the handler, or other middlewares, to do cleanup

import { withMiddlewares } from 'lambda-express-middlewares'

// Your custom middleware, takes in an additional next function, similar to express.
const cleanupMiddleware = async (event, context, next) => {
  try {
    const res = await next(event, context)
    return res
  } catch (e) {
    console.log()
    return { statusCode: 500, body: { message: 'e.message' } }
  } finally {
    // Some code to cleanup
  }
}

// Your regular lambda handler.
const apiHandler = async (event, context) => {
  const result = await someService(event)
  return { statusCode: 200, body: JSON.stringify({ message: 'success' }) }
}

// Export your handler with middlewares.
export const handler = withMiddlewares([validateOrderMiddleware], apiHandler)

Typescript

For examples in typescript, check out the test file in this project. There you will find some examples on how to type your middleware functions.