-
Notifications
You must be signed in to change notification settings - Fork 548
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
3.178.0 may break @aws-sdk/s3-request-presigner getSignedUrl #3983
Comments
looks like this is a dupe of #3981 |
Even i am facing the same issue. Could anyone resolve this |
as a workaround while the issue is fixed, we've added |
I tried this and discovered other packages also seem to be missing from dep tree. |
mdesousa's workaround works. |
This is exactly what I got today. Change to older version fix this problem. |
Even after installing the package separately it shows Cannot find module. Could the owner fix this issue please. Its causing our application to down from 3 days |
@ahmed-sharief5 try using an older version. |
@aitchkhan Please let me know the version number |
Hi @bmccann36, thanks for opening this issue. I can confirm this is an issue and we will work on getting this fixed as soon as possible. In the meantime we have two workarounds. Please see below:
I will use this thread to provide updates accordingly. Thanks! |
Hi @bmccann36, this issue has been fixed by the following PR. Thanks! |
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
3 hours ago there was a release to version 3.178.0. We are using
npm i
notci
in our pipeline so a newer version was installed. We did not change anything in our code but after the new build we started seeing this when our code tried to executeimport {getSignedUrl} from '@aws-sdk/s3-request-presigner'
If we change our package.json from
"@aws-sdk/s3-request-presigner": "^3.178.0"
=>"@aws-sdk/s3-request-presigner": "3.67.0"
it fixes the issue
SDK version number
@aws-sdk/s3-request-presigner@3.178.0
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
node 14 on AWS Lambda
Reproduction Steps
Observed Behavior
Expected Behavior
I am able to call
getSignedUrl
Possible Solution
No response
Additional Information/Context
No response
The text was updated successfully, but these errors were encountered: