You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only the latest version of these modules in the jsdelivr CDN (version 5.2.0) exports the expected keys.
Should @aws-sdk/client-s3 be rebundled to import @5.2.0/+esm versions of these two modules? Or perhaps the @3.0.0/+esm versions of these modules need to be rebundled to include the exports required by @aws-sdk/client-s3?
Thanks for the report. I managed to improve the export detection so that Sha1 and Sha256 are now exported. The change isn't live yet but will be with the next deployment.
Unfortunately, after that, I found there's an issue with another module imported by https://cdn.jsdelivr.net/npm/@aws-sdk/client-s3@3.430.0/+esm as well. There, it's an incorrect use tslib which would I don't think we can/should fix. So even after the issue here is fixed, the client won't work in its current form.
Uncaught SyntaxError: The requested module '/npm/@smithy/hash-blob-browser@2.0.13/+esm' does not provide an export named 'blobHasher' (at jsdelivr-header.js:7:1)
Details of the browser/Node.js/ReactNative version
Chrome Version 123.0.6312.106 (Official Build) (64-bit) on Windows 10
Description
When importing
@aws-sdk/client-s3
using the ESM flag from the latest version:the module tries to import
Sha1
from/npm/@aws-crypto/sha1-browser@3.0.0/+esm
andSha256
from/npm/@aws-crypto/sha256-browser@3.0.0/+esm
.An error results because those keys are not defined as exports of the corresponding jsdelivr CDN modules:
Only the latest version of these modules in the jsdelivr CDN (version 5.2.0) exports the expected keys.
Should
@aws-sdk/client-s3
be rebundled to import @5.2.0/+esm versions of these two modules? Or perhaps the @3.0.0/+esm versions of these modules need to be rebundled to include the exports required by@aws-sdk/client-s3
?Affected jsDelivr links
https://cdn.jsdelivr.net/npm/@aws-sdk/client-s3@3.430.0/+esm
Response headers
Information
Requisites
Additional content
No response
The text was updated successfully, but these errors were encountered: