Maintenance: remove a dependency to deprecated library @aws-sdk/util-base64-node

[yamatatsu]

Summary

Let's remove a deprecated dependency. See, https://www.npmjs.com/package/@aws-sdk/util-base64-node.

Why is this needed?

Following warning is shown on installing @aws-lambda-powertools/parameters;

Which area does this relate to?

Parameters, Idempotency

Solution

About idempotency, remove the dependency because it is not used.
About parameters, replace it to @smithy/util-base64.

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.

[dreamorosi]

Thank you for taking the time to open the issue.

This is a duplicate of #1915, which has a long form explanation of why we kept the dependency around rather than upgrading to the newer one.

Since then, we have invested time in writing our own little utility to convert from base 64 encoded data (#2188), so we should move the Parameters utility to use that instead.

I'm more than happy to review and merge a PR that does that as well as removing the dependency from the Idempotency utility, but I'd be inclined to block the current PR that instead upgrades to the @smithy dependency.

Let me know if that works for you or you have any questions.

[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.0.4 version!