Closed ignaciolarranaga closed 1 year ago
For @aws-sdk it could be removed since AWS Lambda NodeJs Runtime has it. But the others we are not sure, since AWS Lambda does not provide a full list of dependencies by default(and it might be changed without notice?), we cannot guarantee whether XRay SDK work in Lambda after pruning something. So, please prune the dependencies based on your experience if required.
Hi guys, I'm trying to reduce the size of my bundle in a lambda and discovered that the dependencies added by the aws-xray-sdk-core sum a lot, being specific, a project just with this dependency:
Has 5.9M in the node_modules:
Is there a way to prune some of this context?, e.g. @aws-sdk (which is already packaged in the lambda context), @types, semver?
Can I prune it manually for example to just include aws-xray-sdk-core?
Thanks in advance.