Maintenance: Logger unit test fails with Nodejs v22.19.0 in the pipeline

[sdangol]

Summary

One of the unit tests in the Logger utility is failing
https://github.com/aws-powertools/powertools-lambda-typescript/actions/runs/17432536582/job/49494081506

There seems to be an extra parameter diff that was passed in error. This is only seen in v22.19.0. Previous versions of Nodejs didn't pass that parameter.

Why is this needed?

The test is currently failing and blocking the pipeline

Which area does this relate to?

Tests

Solution

We can either make the test less strict by using toMatchObject instead of toEqual.
or, we could just include the diff parameter to be expected.

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.

[dcabib]

Hey! I just reproduced this issue - it's exactly what you described. Node.js v22.19.0+ is adding an extra diff: "simple" property to AssertionError objects, breaking the exact match in the test.

Super easy fix though - just need to add diff: expect.any(String) to the expected fields in the AssertionError test case in formatters.test.ts. I already tested it and it works perfectly.

Want me to submit a PR? I can have this fixed in like 2 minutes. The test is being too strict expecting an exact match when Node.js is now including this extra property. My fix keeps the test precise but accounts for the new property.

Let me know if you want me to handle it!

[dreamorosi]

Thank you, there's a PR already linked.