Undeclared Dependencies in token-providers@3.385.0 #5056
Labels
bug
This issue is a bug.
p2
This is a standard priority issue
queued
This issues is on the AWS team's backlog
workaround-available
This issue has a work around available.
Checkboxes for prior research
Describe the bug
After updating to 3.385.0, using Yarn 3.6.1, there are a number of (21) unresolved dependencies for token-providers.
For example:
This may be related to #5049
Workaround was ultimately the following packageExtension in .yarnrc.yml:
SDK version number
@aws-sdk/token-providers@3.385.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
node v18.17.0
Reproduction Steps
This was observed after a routine update from:
to:
Observed Behavior
Using yarn 3.6.1 (PnP), after building and deploying a docker container, one error would be logged during app startup like the one below. Each time a suitable entry was added to .yarnrc.yml, the next start would reveal a further undeclared dependency.
The error appears to be during initialisation of the S3 component.
Expected Behavior
Clean startup with all dependencies captured during the build phase.
Possible Solution
This may be related to #5049
Workaround was the following packageExtension in .yarnrc.yml:
Additional Information/Context
The last similar issue I saw led to this entry in my .yarnrc.yml:
The text was updated successfully, but these errors were encountered: