@aws-crypto/sha256-browser missing @aws-sdk/util-utf8-browser as a dependency in package.json
See original GitHub issueDescribe the bug
[Package Error] “@aws-sdk/util-utf8-browser” no dependency version info found. (Imported by “@aws-crypto/sha256-browser”).
The package “@aws-crypto/sha256-browser” depends on “@aws-sdk/util-utf8-browser” as a dependency, but did not list any dependency version info in its package manifest. Without this information, the CDN is unable to properly resolve this import.
How to fix: Let the “@aws-crypto/sha256-browser” package author know that “@aws-sdk/util-utf8-browser” needs to be included in their package.json manifest
Your environment
SDK version number
@aws-sdk/client-kms@v3.33.0
Is the issue in the browser/Node.js/ReactNative?
Deno (via skypack.dev)
Details of the browser/Node.js/ReactNative version
deno v1.14.0
Steps to reproduce
Please share code or minimal repo, and steps to reproduce the behavior.
import { KMSClient, GetPublicKeyCommand, SignCommand } from "https://cdn.skypack.dev/@aws-sdk/client-kms?dts";
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:16
Top Results From Across the Web
Integrations AWS S3 API Starter - error with @aws-sdk/client ...
The AWS S3 starter template is throwing this error: AWS = Error: [Package Error] “@aws-sdk/util-utf8-browser” no dependency version info found.
Read more >A module may be missing from 'dependencies' in package.json
I removed the engines part in package.json and now it works. I am assuming its an issue with node versions.
Read more >package.json - npm Docs
The optional files field is an array of file patterns that describes the entries to be included when your package is installed as...
Read more >Manage npm packages - Visual Studio (Windows)
js). npm packages are shown in Solution Explorer. The entries under the npm node mimic the dependencies in the package.json file. Screenshot of ......
Read more >What Is package.json? | heynode.com
In this tutorial, learn how to manage metadata in an initial package.json file such as name, version, description, and keywords, as well as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Also worth noting that various other AWS SDKs are broken generally on (e.g.) Skypack until this change flows back to them. I tested a somewhat random sampling of
@aws-sdk/client-ec2
,@aws-sdk/client-ecs
,@aws-sdk/client-cloudwatch-logs
, and all were broken as of just now.As before, always happy to help, just let me know what I can do. Among other things I’d be happy to help work on tests to make sure this doesn’t happen again.
Thanks @josecorella, I will only be able to verify this works when
@aws-sdk/client-kms
upgrades its crypto dependencies to2.0.0
– unfortunatelyaws-sdk-js-v3
onmain
branch hasn’t updated yet: https://github.com/aws/aws-sdk-js-v3/blob/main/clients/client-kms/package.json#L22-L23and therefore we are still seeing problems with both skypack:
and esm.sh:
Obviously
aws-sdk-js-crypto-helpers@2.0.0
was released just a few hours ago, but do you know how long it will take to incorporate these latest dependencies here intov3
?EDIT
I was able to test the 2.0.0 dependencies with
esm.sh
through the specify external dependencies feature:however, the same error occurred: