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
ibm-cos-sdk is huge on the client side #20
Comments
Yep, Just verified it as well. It looks like the distfile generator is pulling in folders from the source code that should be ignored, including the tests folder which is probably the biggest part. |
Good to know, can it be fixed :-)? |
Looks like I was wrong, and it's because a dependency for |
Even before it was very large (something like 500kb) - is there a chance of analyzing it from the PoV of client (browser) side use and trimming it down further? |
Any updates on this? It is a big problem for Watson Data Platform - it is much larger than the entire page JS chunk. Use in browsers is a legitimate and important use case. |
Will be fixed in the next patch |
What's the ETA for it? |
Delayed pending a license review, not sure on ETA now... |
This has been applied to Release 1.2.1. Please verify on your end whether this clears up or not. If it is correct, please close this issue. Thanks. @dglozic |
Thanks, will switch to it. |
Yup, confirmed that it is down in size now - looks good. Thanks! |
Why is this library so big? When I analyze it in WebPack memory analyzer, it ends up being 1.2MB before compression (366kB after compression). This is huge in comparison to AWS S3 SDK that clocks at only 283kB (70kB after compression).
AWS S3 SDK is obviously optimized so that it can be used on the client side code through WebPack/commonJS. Can you review your dependencies and see if you really need all of them. As it stands now, IBM COS SDK is bordering on unusable on the client side.
The text was updated successfully, but these errors were encountered: