Maintenance: add vitest to project

[dreamorosi]

Summary

In the past weeks we have been experimenting with moving our test suites to Vitest with good results. We will now start gradually switching our test suites from Jest to Vitest.

As a first step, we should add the package to the project so that in future issues we will be able to target each package in the workspace separately.

Why is this needed?

So that we can move our environment to fully default to ESM rather than using CJS and converting things on the fly when running tests.

Additionally, moving to Vitest will allow us to run our tests in the CI without having to build our TypeScript code first.

Which area does this relate to?

Tests

Solution

No response

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.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v2.8.0 version!