Dependencies mismatch across some packages #6613
Labels
feature-request
New feature or enhancement. May require GitHub community feedback.
p3
This is a minor priority issue
queued
This issues is on the AWS team's backlog
Checkboxes for prior research
Describe the bug
We have the following dependency chain:
@aws-sdk/client-s3@npm:3.682.0
->@aws-crypto/sha1-browser@npm:5.2.0
-> @smithy/util-utf8@npm:2.3.0Which is not compatible with other SDK packages' chains, e.g.:
@aws-sdk/client-dynamodb@npm:3.682.0
->@smithy/util-utf8@npm:3.0.0
@aws-sdk/client-iot
->@smithy/util-utf8@npm:3.0.0
@aws-sdk/middleware-sdk-s3@npm:3.682.0
->@smithy/util-utf8@npm:3.0.0
This causes two different versions of
@smithy/util-utf8
and its dependecies to be bundled in our app.There are also issues with some semver declarations in other packages, e.g.:
@aws-sdk/client-sqs@npm:3.682.0
->@aws-sdk/middleware-sdk-sqs@npm:3.679.0
(3.679.0
is fixed).Regression Issue
SDK version number
@aws-sdk/*@3.682.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
v21.7.3
Reproduction Steps
N/A.
Observed Behavior
See description.
Expected Behavior
Versioning of the SDK packages to be consistent to avoid different versions of modules being bundled together.
Possible Solution
Make sure all packages are bumped together and that correct semver syntax is being used when declaring dependencies.
In the meantime, we are using Yarn Resolutions to mitigate. However, this is risky across major versions like in the case of
@smithy/util-utf8@npm:2.3.0
/@smithy/util-utf8@npm:3.0.0
.Additional Information/Context
N/A.
The text was updated successfully, but these errors were encountered: