A type safe and modern jmespath module to parse and extract data from JSON documents using JMESPath
npm install @aws-lambda-powertools/jmespathPowertools for AWS Lambda (TypeScript) is a developer toolkit to implement Serverless best practices and increase developer velocity.
You can use the package in both TypeScript and JavaScript code bases.
- Intro
- Usage
- Basic usage
- Extract data from envelopes
- JMESPath custom functions
- Contribute
- Roadmap
- Connect
- How to support Powertools for AWS Lambda (TypeScript)?
- Becoming a reference customer
- Sharing your work
- Using Lambda Layer
- License
The JMESPath utility is a high-level function to parse and extract data from JSON objects using JMESPath expressions.
To get started, install the library by running:
``sh`
npm i @aws-lambda-powertools/jmespath
At its core, the library provides a utility function to extract data from a JSON object using a JMESPath expression.
`ts
import { search } from '@aws-lambda-powertools/jmespath';
import { Logger } from '@aws-lambda-powertools/logger';
const logger = new Logger();
type MyEvent = {
foo: {
bar: string;
};
}
export const handler = async (event: MyEvent): Promise
const result = search(event, 'foo.bar');
logger.info(result); // "baz"
};
`
In some cases, you may want to extract data from an envelope. The library provides a utility function to help you work with envelopes and extract data from them.
`ts
import { extractDataFromEnvelope } from '@aws-lambda-powertools/jmespath/envelopes';
type MyEvent = {
body: string; // "{\"customerId\":\"dd4649e6-2484-4993-acb8-0f9123103394\"}"
deeplyNested: Array<{ someData: number[] }>;
};
type MessageBody = {
customerId: string;
};
export const handler = async (event: MyEvent): Promise
const payload = extractDataFromEnvelope
event,
'powertools_json(body)'
);
const { customerId } = payload; // now deserialized
// also works for fetching and flattening deeply nested data
const someData = extractDataFromEnvelope
event,
'deeplyNested[*].someData[]'
);
return {
customerId,
message: 'success',
context: someData,
statusCode: 200,
};
};
`
The library provides a set of built-in envelopes to help you extract data from common event sources, such as S3, SQS, and SNS, and more.
`ts
import {
extractDataFromEnvelope,
SQS,
} from '@aws-lambda-powertools/jmespath/envelopes';
import { Logger } from '@aws-lambda-powertools/logger';
import type { SQSEvent } from 'aws-lambda';
const logger = new Logger();
type MessageBody = {
customerId: string;
};
export const handler = async (event: SQSEvent): Promise
const records = extractDataFromEnvelope
for (const record of records) {
// records is now a list containing the deserialized body of each message
const { customerId } = record;
logger.appendKeys({ customerId });
}
};
`
In addition to all the built-in JMESPath functions, the library provides custom functions to help you work with complex data structures. For example, you can use the powertools_json function to parse a JSON string, or the powertools_base64 function to decode a base64-encoded string:
`ts
import { extractDataFromEnvelope } from '@aws-lambda-powertools/jmespath/envelopes';
import { Logger } from '@aws-lambda-powertools/logger';
const logger = new Logger();
export const handler = async (event: { payload: string }): Promise
const data = extractDataFromEnvelope
event,
'powertools_json(powertools_base64(payload))'
);
logger.info('Decoded payload', { data });
};
`
Finally, you can also extend the library with your own custom functions. Below an example of how to create a custom function to decode a Brotli-compressed string.
`ts
import { fromBase64 } from '@aws-lambda-powertools/commons/utils/base64';
import { extractDataFromEnvelope } from '@aws-lambda-powertools/jmespath/envelopes';
import { PowertoolsFunctions } from '@aws-lambda-powertools/jmespath/functions';
import { Logger } from '@aws-lambda-powertools/logger';
import { brotliDecompressSync } from 'node:zlib';
const logger = new Logger();
class CustomFunctions extends PowertoolsFunctions {
@PowertoolsFunctions.signature({
argumentsSpecs: [['string']],
variadic: false,
})
public funcDecodeBrotliCompression(value: string): string {
const encoded = fromBase64(value, 'base64');
const uncompressed = brotliDecompressSync(encoded);
return uncompressed.toString();
}
}
export const handler = async (event: { payload: string }): Promise
const message = extractDataFromEnvelope
event,
'Records[].decode_brotli_compression(notification) | [].powertools_json(@).message',
{ customFunctions: new CustomFunctions() }
);
logger.info('Decoded message', { message });
};
`
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:
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:
- Alma Media
- AppYourself
- Bailey Nelson
- Banxware
- Caylent
- Certible
- Codeac
- EF Education First
- Elva
- Flyweight
- FraudFalcon
- globaldatanet
- Guild
- Hashnode
- Instil
- LocalStack
- Ours Privacy
- Perfect Post
- Sennder
- tecRacer GmbH & Co. KG
- Trek10
- WeSchool
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).
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.