Closed EricCrosson closed 3 years ago
The second bug mentioned appears to be this one: https://github.com/aws/aws-sdk-js-v3/issues/1842, so no need to focus on it here. This workaround worked for me.
The root cause for this issue seems to be duplicated with #1842. We will make comments there as we progress.
Agreed, ok thanks. Will close this ticket out then
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Describe the bug
SDK version number
3.1.0
Is the issue in the browser/Node.js/ReactNative?
Node.js
Details of the browser/Node.js/ReactNative version
To Reproduce (observed behavior)
I followed instruction from this comment: https://github.com/aws/aws-sdk-js/issues/3018#issuecomment-725817099
npx tsc
This results in the following compilation errors from within the @aws-sdk/util-dynamodb package:
Expected behavior
I expected compilation to succeed.
Additional context
If there is a dependency on the client-dynamodb package from the util-dynamodb package, maybe expressing this as a range in the peerDependency field of the util-dynamodb package.json would suffice. npm 7 would then resolve this peerDependency during
npm install
and there would be no error.Note that installing @aws-sdk/client-dynamodb I get a different error:
which I am less certain how to get past. This one seems like an internal bug
Update: this second bug is already reported