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

@shgysk8zer0/lambda-http

v1.1.19

Published

A collection of node >= 20 utilities for Netlify Functions and AWS Lambda

Downloads

60

Readme

@shgysk8zer0/lambda-http

A collection of node >= 20 utilities for Netlify Functions and AWS Lambda

CodeQL Node CI Lint Code Base

GitHub license GitHub last commit GitHub release GitHub Sponsors

npm node-current npm bundle size gzipped npm

GitHub followers GitHub forks GitHub stars Twitter Follow

Donate using Liberapay


This package makes use of node >= 20 having support for the familiar Request & Response objects to provide easier and more standards-based way of creating Netlify Functions and (theoretically) AWS Lambda.

Benefits

  • Familiar Request & Response objects
  • Built-in support for FormData & Files & Blobs
  • Easy support for CORS while still being customizable
  • Convenient { [method]: async handler(requset) } syntax
  • Constants for HTTP Status Codes & common Mime-Types
  • A custom HTTPError class
  • Currently weighs in at only 42.5 kB (unpacked size, including ESM & CJS & & README LICENSE & CHANGELOG)

Example

import { createHandler, HTTPError, HTTP_STATUS } from '@shgysk8zer0/lambda-http';

export default createHandler({
  async get(req) {
    return Response.json({
      url: req.url,
      method: req.method,
      headers: Object.fromEntries(req.headers),
    });
  },
  async post(req) {
    const data = await req.formData();
    // Or `req.json()`

    if (! (data.has('email') && data.has('password'))) {
      throw new HTTPError('Email and password are required', HTTP_STATUS.BAD_REQUEST);
    } else {
      // Sign-in logic here
      return Response.json(user);
    }
  },
  async put(req) {
    const blob = await req.blob();
    // Or use `req.arrayBuffer()`
    // Maybe save it as a file...

    return new Response(null, { status: HTTP_STATUS.NO_CONTENT });
  }
  async delete(req) {
    const params = new URLSearchParams(req.url);

    if (params.has('id')) {
      // Handle some delete operation
    } else {
      throw new HTTPError('Missing required id.', HTTP_STATUS.BAD_REQUEST);
    }
  }
}, {
  allowOrigins: ['https://example.com'],
  allowHeaders: ['Authorization'],
  exposeHeaders: ['X-Foo'],
  allowCredentials: true,
  logger(err, req) {
    console.error({ err, req });
  }
});

CommonJS (require()) Note

This is primarily intended for use with ES Modules, though CJS files are generated via Rollup. Because of this, bear in mind that default exports and named exports do not perfectly translate, and you cannot just use const createHandler = require('@shgysk8zer0/lambda-http') like you can with modules. You'll have to use const { createHandler } = require('@shgysk8zer0/lambda-http') or const { default: createHandler } = require('@shgysk8zer0/lambda-http').