Jan 6, 2025: end of support for Node.js 16.x in AWS SDK for JavaScript (v3)

[trivikr]

Starting January 6, 2025, the AWS SDK For JavaScript (v3) will no longer support Node.js 16.x, which reached end-of-life on September 11, 2023.

We encourage you to upgrade to a Node.js Active Long Term Support (LTS) version, which is Node.js 20.x as of July 2024.

More details in blog post Announcing the end of support for Node.js 16.x in the AWS SDK for JavaScript (v3)

[trivikr]

This issue is for announcement and can be closed when support for Node.js <18.x ends on Jan 6, 2025.

[aBurmeseDev]

Effective today, January 6, 2025, the AWS SDK For JavaScript (v3) will no longer support for Node.js 16.x, which reached its end-of-life on September 11, 2023.

We encourage you to upgrade to a Node.js Active Long Term Support (LTS) version, which is Node.js 22.x as of January 2025. For AWS Lambda users specifically, AWS Lambda now supports Node.js 22.

For those who's come across this post, It's worth noting that

....If you are using Node.js 16.x, installing the later versions of the SDK will cause an engine deprecation warning to appear. If you have set engine-strict=true, an NPM installation error with code ENOTSUP will occur as follows.

$ node --version
v16.20.2

$ npm install @aws-sdk/client-s3
...
npm ERR! code ENOTSUPnpm ERR! notsup Unsupported engine for aws-sdk@<version>: wanted: {"node":">=18.0.0"} (current: {"node":"16.20.2","npm":"8.19.4"})
...

For further details, please refer to our blog post.

[ThermScissorpunch]

Does this means it doesn't work at all anymore? Or only feature updates?

[kuhe]

https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.722.0 and prior releases continue to work with Node.js 16.

Higher versions may work with some versions of Node.js 16.11.0+, but if they stop working we will not make changes to fix them for Node.js 16. In the same manner, no future feature updates will include support for Node.js 16.