Maintenance: add ESM builds to integration tests

[dreamorosi]

Summary

As part of our automation we run integration tests on the Powertools packages by deploying Lambda functions into an ephemeral infrastructure on AWS.

As of now we test all the features and utilities that directly interact with AWS services and can change their behavior when run in a AWS Lambda execution environment. In doing so, we test all the Node.js versions supported as managed runtimes by Lambda. Additionally, we also run the tests for both x86 and arm64 architectures.

In v2 we released ESM support, but as of now we don't include this build mode in our tests. We should change that.

Why is this needed?

So that we can increase the confidence in our published artifacts.

Which area does this relate to?

Automation

Solution

Switch some of the functions deployed as part of the integration tests to be bundled as ESM and have at least one function for each package using ESM.

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.