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
Thank you for your work.
We are using this library in context where size matters and we noticed this module brings along the entire aws-sdk.
Is there a way to import the S3 client only?
See attached web pack report.
Thank you,
Ra
The text was updated successfully, but these errors were encountered:
This library was mostly meant to be used in tooling (as cli, or from node), so it hasn't been designed in this way.
Looking at the v2 AWS SDK, it might not even be possible.
So for this request we would need to migrate this library to use the v3 SDK.
Additional, I see some other modules are used that are more meant to work in a node environment (like globbing, path resolving), so potentially some extra work would need to be done to make those dependencies optional as well.
Have you verified that this module is actually working (besides the side constraints) in your context? (or is Node still your context, but you like to limit file bundle size?)
Thanks for your quick response.
We're using it in a node environment, on some slow connections on machines with a one liner download & execute script. This reduces maintenance/versioning work across multiple machines.
Having said that, since 2.6.0 It is possible to import only portions of the sdk.
Hi,
Thank you for your work.
We are using this library in context where size matters and we noticed this module brings along the entire aws-sdk.
Is there a way to import the S3 client only?
See attached web pack report.
Thank you,
Ra
The text was updated successfully, but these errors were encountered: