-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Snowpack build fails with aws-sdk 3.4.1 #7762
Comments
Hello! I was able to reproduce this. We will look to upgrade our npm i @aws-amplify/[email protected] --save --save-exact
# or
npm i [email protected] --save --save-exact |
The workaround causes heap overflow in my machine. I saw that this bug was fixed here. Is there any sense of when it will be released? |
@bhavinkamani-gt @volkanunsal This has been now released! Please install a fresh copy of |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Describe the bug
A clear and concise description of what the bug is.
Issue aws/aws-sdk-js-v3#1992 was breaking my snowpack build. Patch aws/aws-sdk-js-v3#1991 has been released as part of 3.5.0. Kindly upgrade the dependency.
Following error is thrown while running snowpack build
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
build should succeed
Code Snippet
Please provide a code snippet or a link to sample code of the issue you are experiencing to help us reproduce the issue. (Be sure to remove any sensitive data)
NA
Screenshots
If applicable, add screenshots to help explain your problem.
NA
What is Configured?
If applicable, please provide what is configured for Amplify CLI:
NA
Smartphone (please complete the following information):
CLI
Additional context
Add any other context about the problem here.
You can turn on the debug mode to provide more info for us by setting window.LOG_LEVEL = 'DEBUG'; in your app.
The text was updated successfully, but these errors were encountered: