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

aws-lambda-response

v1.1.0

Published

A simple package for building standard responses in AWS Lambda callback functions.

Downloads

2

Readme

aws-lambda-response Build Status

A simple package for building standard responses in AWS Lambda callback functions to be handled by API Gateway.

Install

$ npm install --save aws-lambda-response

Why

API Gateway does not support objects as the error parameter in callbacks from Lambda, this package solves this by stringifying error and failure responses and assumes the JSON is parsed at API Gateway level.

Usage

import resp from 'aws-lambda-response';

function handler(event, context, callback) {
  callback(null, resp.success(200, { hello: "World"}));
}

export { handler };

API

The following API is based on the imported module being named resp, however it can be substituted for any name you want.

// ES6 modules
import resp from 'aws-lambda-response';

// commonJS modules
const resp = require('aws-lambda-response');

resp.success(statusCode, data)

Params

statusCode

Type: int

HTTP status code to be mapped in the API Response header

data

Type: object

Response payload.

Returns

Type: object

{
  status: "success",
  httpStatus: (int)statusCode,
  data: (obj)data
}

resp.error(statusCode, message, data)

Params

statusCode

Type: int

HTTP status code to be mapped in the API Response header

message

Type: string

Error message

data

Type: object

Any additional response data.

Returns

Type: string

Stringified object to be parsed in API Gateway output mapping.

{
  "status": "error",
  "httpStatus": "(int)statusCode",
  "message": "(string)message",
  "data": "(object)data"
}

resp.fail(statusCode, data)

Params

statusCode

Type: int

HTTP status code to be mapped in the API Response header

data

Type: object

Response data that may help explain the issue. Can be be a string if the information is better presented as one.

Returns

Type: string

Stringified object to be parsed in API Gateway output mapping.

{
  "status": "fail",
  "httpStatus": "(int)statusCode",
  "data": "(object)data"
}

License

MIT