aws-sdk/types@^3.1.0 dependency generates error TS2305 with aws-sdk/* since 3.54.1
#337
Comments
texastony
added a commit
to texastony/aws-sdk-js-crypto-helpers
that referenced
this issue
Jun 21, 2022
texastony
added a commit
that referenced
this issue
Jun 21, 2022
|
Hello @KeithGillette! Thank you for bringing this to our attention; we have put out a fix and released it. You should be able to pick it up in the latest version of the @aws-crypto packages. |
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per
@aws-sdkissue #3437, I believe a PR incorporated into@aws-sdk/*@3.54.1, which moved several types from@aws-sdk/shared-ini-file-loaderinto@aws-sdk/types, generated an incompatibility withaws-cryptopackages depending onaws-sdk/types@^3.1.0, resulting in error TS2305 when runningtscon a project with the defaulttsconfig.jsonskipLibCheck: false.In testing with a project dependent upon
@aws-crypto/sha256-browser@2.0.1, forcing installation of@aws-sdk/types@latestprevents the TS2305 error. Can@aws-cryptopackages be updated to a newer@aws-sdk/typescompatible with the latest@aws-sdkreleases?The text was updated successfully, but these errors were encountered: