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

@jschr/lambda-response

v0.1.8

Published

Express-like API for sending responses from Lambda Integration Proxy to API Gateway and a CLI for local development.

Downloads

5

Readme

lambda-response

npm Build Status

Express-like API for sending responses from Lambda Integration Proxy to API Gateway.

Includes a CLI tool and express middleware for local development.

Install

npm install @jschr/lambda-response

Usage

const { Response } = require('@jschr/lambda-response')

export default function handler(event, context) {
  const res = new Response()

  context.succeed(res.send('OK'))
  // => { statusCode: 200, body: 'OK' }

  context.succeed(res.json({ foo: bar }))
  // => { statusCode: 200, body: '{"foo":"bar"}' }

  context.succeed(res.status(404).json({ message: 'Not found.' }))
  // => { statusCode: 404, body: '{"message":"Not found."}' }

  context.succeed(res.redirect('https://github.com'))
  // => { statusCode: 302, headers: { Location: 'https://github.com'} } }
}

Even more express-like with async/await:

const { Response } = require('@jschr/lambda-response')

async function route(req, res) {
  const data = await someAsyncFunction(req.query.id)

  if (data) {
    res.json(data)
  } else {
    res.status(404).json({ message: 'Not found'. })
  }
}

export default function handler(event, context) {
  const req = { query: event.queryStringParameters || {} }
  const res = new Response()

  route(req, res)
    .then(() => context.succeed(res))
    .catch(context.fail)
}

Headers

Default headers can be passed when creating a new response:


const headers = { 'Content-Type': 'application/json' }
const res = new Response({ headers })

Or on an instance:


const res = new Response()
const headers = { 'Content-Type': 'application/json' }
res.set(headers)

CORS

CORS is enabled by default. You can pass in cors options when creating a new response:

const cors = { origin: 'example.com', methods: ['GET'], headers: ['X-Api-Key'] }
const res = new Response({ cors })

Check out the tests for more examples.

CLI

You can use the CLI for local development. If you've installed @jschr/lambda-response globally:

$ lambda-response foo/bar.default --port 8080

Where foo/bar is the path to your lambda handler and default is the exported function.

Middleware

For advanced use cases you can use the lambda-response express middleware:

import * as express from 'express'
import { middleware } from '@jschr/lambda-response'

import handler from './foo/bar'

const app = express()

app.use(middleware(handler))

app.listen(8080)