feat: use caret range for aws-sdk deps #14425
Open
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.
Description of changes
This pull request migrates all aws-sdk dependencies to use caret version range.
The aws-sdk is a rather large dependency, and most of it's packages are highly entangled and depend on fixed versions, i.e. adding a single package as a dependency installs quite a few other packages from aws-sdk.
As an example, installing
@aws-sdk/client-firehose
(a dep of @aws-amplify/analytics) adds 22 different aws-sdk packages.This becomes quite annoying if depending on aws-sdk myself, as it will result in a lot of duplicate packages with varying versions, or alternatively forcing me to use the same (old) version that aws-amplify depends on.
The aws-sdk is strict on not introducing breaking changes, so I see no reasing enforcing a specific version :)
Checklist
yarn test
passesChecklist for repo maintainers
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.