Migrate AWS SDK for JavaScript from v2 to v3 #1730
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alphadev4
approved these changes
Nov 27, 2023
nuhasha
force-pushed
the
nuhasha/MigrateAWSSDK
branch
from
4e9b928 to
49d70cb
Compare
|
What happened here? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
node is formalizing plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.
We need to migrate code to use AWS SDK for JavaScript (v3).
Migration guide: https://www.npmjs.com/package/aws-sdk-js-codemod