Skip to content

@aws-crypto/kms-keyring-node dependency issue #922

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

Closed
d3mi3n opened this issue May 24, 2022 · 3 comments
Closed

@aws-crypto/kms-keyring-node dependency issue #922

d3mi3n opened this issue May 24, 2022 · 3 comments

Comments

@d3mi3n
Copy link

d3mi3n commented May 24, 2022

Problem:

@aws-crypto/kms-keyring-node imports @aws-crypto/material-management in this file, but @aws-crypto/material-management is not listed as a dependency

Solution:

Add @aws-crypto/material-management as a dependency of @aws-crypto/kms-keyring-node or (if possible) use @aws-crypto/material-management-node which is a dependency already.

@ajewellamz
Copy link
Contributor

#1018

@trevorpoppen
Copy link

Hello, I'm seeing this dependency issue rear it's head again in "@aws-crypto/client-node": "^3.2.0" ;

Import throwing the error is import { NodeAlgorithmSuite } from '@aws-crypto/material-management'; from @aws-crypto/kms-keyring-node;

I'm using PlugnPlay in Yarn 3.3.0 and typescript 4.9.3

@josecorella
Copy link
Contributor

Hello @d3mi3n,

Major Version 4.0.0 of the AWS ESDK for JS has been released. This major version should address the problems you outline on this issue. Please let us know if you have any questions.

AWS Crypto Tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants