Powertools for AWS Lambda (TypeScript) is a developer toolkit to implement Serverless best practices and increase developer velocity.

You can use the library in both TypeScript and JavaScript code bases.

The Commons package contains a set of utilities that are shared across one or more Powertools for AWS Lambda (TypeScript) utilities. Some of these utilities can also be used independently in your AWS Lambda functions.

To get started, install the utility by running:

npm i @aws-lambda-powertools/commons

When working with different objects and values, you may want to do runtime type checks. The utility comes with a set of type utilities that you can use to check the type of an object or value.

import { isRecord } from '@aws-lambda-powertools/commons/typeUtils';
import { isString } from '@aws-lambda-powertools/commons/typeUtils';
import { isTruthy } from '@aws-lambda-powertools/commons/typeUtils';


const value = { key: 'value' };
if (isRecord(value)) {
  // value is a record
}

const stringValue = 'string';
if (isString(stringValue)) {
  // stringValue is a string
}

const truthyValue = 'true';
if (isTruthy(truthyValue)) {
  // truthyValue is truthy
}

Here's a full list of type utilities available in the package:

• isInteger
• isNull
• isNullOrUndefined
• isNumber
• isRecord
• isStrictEqual
• isString
• isTruthy

Many of these utilities also double as type guards, which you can use to narrow down the type of an object or value.

When working with Base64-encoded data, you can use the fromBase64 utilities to quickly decode data and convert it to a Uint8Array.

import { fromBase64 } from '@aws-lambda-powertools/commons/utils/base64';

const encodedValue = 'aGVsbG8gd29ybGQ=';

const decoded = fromBase64(encodedValue);
// new Uint8Array([ 97, 71, 86, 115, 98, 71, 56, 103, 100, 50, 57, 121, 98, 71, 81, 61 ]); 

In some cases, you may want to define a type for a JSON object or value. The utility comes with a set of types that you can use to define your JSON objects.

import type { JSONValue, JSONObject, JSONArray } from '@aws-lambda-powertools/commons';

When using object-oriented patterns to define your Lambda handlers, you can use the LambdaHandler interface to define the shape of your handler methods.

import type { Context } from 'aws-lambda';
import type { LambdaInterface } from '@aws-lambda-powertools/commons/types';

class Lambda implements LambdaInterface {
  public handler = async (event: unknown, context: Context) => {
    // Your handler code here
  }
}

const handlerClass = new Lambda();
export const handler = lambda.handler.bind(lambda);

If you are interested in contributing to this project, please refer to our Contributing Guidelines.

The roadmap of Powertools for AWS Lambda (TypeScript) is driven by customers’ demand.
Help us prioritize upcoming functionalities or utilities by upvoting existing RFCs and feature requests, or creating new ones, in this GitHub repository.

• Powertools for AWS Lambda on Discord: #typescript - Invite link
• Email: aws-lambda-powertools-feedback@amazon.com

Knowing which companies are using this library is important to help prioritize the project internally. If your company is using Powertools for AWS Lambda (TypeScript), you can request to have your name and logo added to the README file by raising a Support Powertools for AWS Lambda (TypeScript) (become a reference) issue.

The following companies, among others, use Powertools:

• Hashnode
• Trek10
• Elva
• globaldatanet
• Bailey Nelson
• Perfect Post
• Sennder
• Certible
• tecRacer GmbH & Co. KG
• AppYourself
• Alma Media

Share what you did with Powertools for AWS Lambda (TypeScript) 💞💞. Blog post, workshops, presentation, sample apps and others. Check out what the community has already shared about Powertools for AWS Lambda (TypeScript) here.

This helps us understand who uses Powertools for AWS Lambda (TypeScript) in a non-intrusive way, and helps us gain future investments for other Powertools for AWS Lambda languages. When using Layers, you can add Powertools as a dev dependency to not impact the development process.

This library is licensed under the MIT-0 License. See the LICENSE file.