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

@miermontoto/lambda-responses

v1.0.1

Published

Standardized HTTP response helpers for AWS Lambda functions

Readme

@miermontoto/lambda-responses

npm

Consistent HTTP response helpers for AWS Lambda functions. Provides type-safe response methods for all standard HTTP status codes with automatic CORS headers and error formatting.

Installation

pnpm add @miermontoto/lambda-responses

Configuration

interface ResponseOptions {
  headers?: Record<string, string>;
  cors?: boolean;  // default true
}

interface ErrorResponseOptions {
  statusCode?: number;
  error?: string;
  details?: any;
}

Usage

import { ok, badRequest, serverError, notFound } from '@miermontoto/lambda-responses';
import { APIGatewayProxyHandlerV2 } from 'aws-lambda';

export const handler: APIGatewayProxyHandlerV2 = async (event) => {
  try {
    // validate input
    if (!event.body) {
      return badRequest('Request body is required');
    }

    // process request
    const data = JSON.parse(event.body);

    // return success
    return ok({
      message: 'Success',
      data: data
    });

  } catch (error) {
    // return error
    return serverError(error);
  }
};

Available Methods

Success Responses

  • ok(body?, options?) - 200 OK
  • created(body?, options?) - 201 Created
  • noContent(options?) - 204 No Content

Client Error Responses

  • badRequest(message?, options?) - 400 Bad Request
  • unauthorized(message?, options?) - 401 Unauthorized
  • forbidden(message?, options?) - 403 Forbidden
  • notFound(message?, options?) - 404 Not Found
  • conflict(message?, options?) - 409 Conflict
  • unprocessableEntity(message?, options?) - 422 Unprocessable Entity
  • tooManyRequests(message?, options?) - 429 Too Many Requests

Server Error Responses

  • serverError(message?, options?) - 500 Internal Server Error
  • badGateway(message?, options?) - 502 Bad Gateway
  • serviceUnavailable(message?, options?) - 503 Service Unavailable

Other

  • customResponse(statusCode, body, options?) - Custom status code
  • redirect(location, statusCode?) - Redirect response
  • createResponse(statusCode, body, options?) - Base response builder

License

CC BY-NC-ND 4.0