-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to resolve module @aws-sdk/chunked-blob-reader when using S3Client #4631
Comments
Seeing this in latest: |
Looks like this was the PR that removed the dep. #4571 |
I ended up installing these version for now, essentially prior to the removal. And it appears to be working.
|
Hello @coofzilla did you manage a solution, bug is still there. |
Install @aws-sdk/chunked-blob-reader-native |
Any update on this? Still not able to go any higher than 3.298.0. |
Hey @cpyle0819, Thanks for the investigation. I will assign a higher priority for this and try to get this fixed asap. |
Hi @dpyeates @rveramx @Hudson-AmalembaL @coofzilla , @cpyle0819 , We just pushed a fix that reintroduces the missing dependency. Thanks 👍 , |
The fix is in https://github.com/awslabs/smithy-typescript/releases/tag/%40smithy%2Fhash-blob-browser%401.0.2 When updating, ensure that this package version is being used in any lockfiles you may have. For example, a fresh install of https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.367.0 should bring in the above package. |
Still not working for me. Using
I am getting the following error: /node_modules/@smithy/util-stream/dist-cjs/getAwsChunkedEncodingStream.js: stream could not be found |
@RanVaknin I'm getting the same error as @dpyeates. Happens when running locally.
|
This updates the @AWS-SDK packages to fix a bug (aws/aws-sdk-js-v3#4631). Unfortunately, another issue has popped up after these updates. I commented on the above ticket my findings. As a result, this example is still broken.
This updates the @AWS-SDK packages to fix a bug (aws/aws-sdk-js-v3#4631). Unfortunately, another issue has popped up after these updates. I commented on the above ticket my findings. As a result, this example is still broken.
This updates the @AWS-SDK packages to fix a bug (aws/aws-sdk-js-v3#4631).
This updates the @AWS-SDK packages to fix a bug (aws/aws-sdk-js-v3#4631).
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. |
Checkboxes for prior research
Describe the bug
Xcode 14.2
Build version 14C18
ProductName: macOS
ProductVersion: 13.2.1
BuildVersion: 22D68
I am trying to use the
S3Client
from the@aws-sdk/client-s3
package in my React Native project, but I am encountering an error related to a missing dependency:@aws-sdk/chunked-blob-reader
. Can someone help me resolve this issue or let me know what I'm missing?package.json
:Additionally, I checked that I do have the required dependency.
SDK version number
"@aws-sdk/client-s3": "^3.18.0",
Which JavaScript Runtime is this issue in?
React Native
Details of the browser/Node.js/ReactNative version
node -v v16.19.0, "react-native": "0.71.6"
Reproduction Steps
Steps to reproduce:
Create a new React Native project.
Install the required AWS SDK packages.
Follow the example code provided in the AWS SDK for JavaScript documentation.
https://github.com/awsdocs/aws-doc-sdk-examples/blob/main/javascriptv3/example_code/reactnative/App.js
Run the project and error pops up.
Observed Behavior
When trying to use the S3Client in a React Native project, the application encounters the following error:
The error occurs even when following the example repository provided in the AWS documentation:
https://github.com/awsdocs/aws-doc-sdk-examples/blob/main/javascriptv3/example_code/reactnative/App.js
Expected Behavior
I expected the S3Client to be imported and successfully initialized without any Errors. After following the example provided in the AWS documentation, I expected to be able to use the S3Client to upload a blob of video data to an S3 bucket.
Possible Solution
No response
Additional Information/Context
Here is the snippet for my actual use case; however, I was able to observe the error even in a brand new project with no configuration.
The text was updated successfully, but these errors were encountered: