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
This package seems really cool and I would love to be able to use it. However, it looks like it pulls in about 20M of dependencies on a fresh install, it looks like mainly owing to the peer dependencies for @aws-sdk/client-s3 and @aws-sdk/s3-request-presigner.
$ mkdir example &&cd example
$ npm init -y
$ npm install --save lambda-api
$ du -h node_modules | tail -n 1
# 20M node_modules
For users who may not have a need to interact with S3, is there a way for these dependencies to be eliminated, or for some configuration to be passed in that skips installing these? If these dependencies are required, could the README be updated to reflect that the package is not dependency free?
The text was updated successfully, but these errors were encountered:
This package seems really cool and I would love to be able to use it. However, it looks like it pulls in about 20M of dependencies on a fresh install, it looks like mainly owing to the peer dependencies for
@aws-sdk/client-s3
and@aws-sdk/s3-request-presigner
.For users who may not have a need to interact with S3, is there a way for these dependencies to be eliminated, or for some configuration to be passed in that skips installing these? If these dependencies are required, could the README be updated to reflect that the package is not dependency free?
The text was updated successfully, but these errors were encountered: