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 🙏

© 2026 – Pkg Stats / Ryan Hefner

lambda-api-helper

v0.0.15

Published

Simplify lambda API creation with middleware support.

Readme

Simplify lambda API creation with middleware support.

Installation

npm install lambda-api-helper

Usage

Quick start

import { lambda } from "lambda-api-helper";

export const hello = lambda.extend(
  async (request, response) => {
    return { hello: "world" };  
  }
);

More Options

It accepts first parameter for more options, which configure each route specifically.

export const hello = lambda.extend(
  {
    initialize() {
      // some route-specific initialization here 
    },
    middlewares: [
      async (request, response, next) => {
        // runs middleware before request         
      
        await next();
        
        // runs middleware after response
      },
    ],
  },
  async (request, response) => {
    return "Hello World";
  }
);

Common configurations

It also allows configuring common initialization and middlewares globally.

lambda.commons.configure({
  initialize() {
    // some global initializations
  },
  middlewares: [
    // some global middlewares
  ],
})

Sending Response

There are 4 ways for sending a response.

  1. return the response in the handler. The content will be automatically stringify if it is object-like.
  2. Call response.send(content) to immediately send your content
  3. Set your content by response.body(content), it will be collected and send after all middlewares ran
  4. Call original callback() provided by AWS. It is located at response.callback()

Test

npm run test

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

BSD 3-Clause