Skip to content
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

Please check whether you have installed the "@aws-sdk/crc64-nvme-crt" package explicitly #2472

Open
sobolk opened this issue Jan 31, 2025 · 1 comment
Labels
bug Something isn't working dependency Issue related to upstream dependency

Comments

@sobolk
Copy link
Member

sobolk commented Jan 31, 2025

Certain versions of AWS SDK v3 can throw

Error: Please check whether you have installed the @aws-sdk/crc64-nvme-crt package explicitly. 
You must also register the package by calling [require(@aws-sdk/crc64-nvme-crt);] or an ESM equivalent such as [import @aws-sdk/crc64-nvme-crt;]. 
For more information please go to https://github.com/aws/aws-sdk-js-v3#functionality-requiring-aws-common-runtime-crt	

Amplify customers can see this message while deploying backend resources.

To resolve the problem please upgrade @aws-sdk/client-s3 to 3.735.0 or later in your project.

Related reports in SDK repository:
aws/aws-sdk-js-v3#6855
aws/aws-sdk-js-v3#6822

@sobolk sobolk added bug Something isn't working dependency Issue related to upstream dependency pending-triage Incoming issues that need categorization labels Jan 31, 2025
@josefaidt josefaidt removed the pending-triage Incoming issues that need categorization label Jan 31, 2025
@kuhe
Copy link

kuhe commented Jan 31, 2025

The AWS SDK for JavaScript team has added a deprecation message to v3.729.0 through v3.734.0 of @aws-sdk/client-s3 calling out this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dependency Issue related to upstream dependency
Projects
None yet
Development

No branches or pull requests

3 participants