-
Notifications
You must be signed in to change notification settings - Fork 375
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
GCS - NPM dependencies #207
Comments
This is something we're actively looking to fix. Most of those dependencies come in with |
Axios? No dependencies and does the job rather well... Thanks for the
update!
…On Fri, Jun 1, 2018, 03:12 Justin Beckwith ***@***.***> wrote:
This is something we're actively looking to fix. Most of those
dependencies come in with request, so removing that is somewhat delicate
work. We are actively working towards it though :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#207 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALpkTPrw9Ri_3yrCZORYICEZg4ccVXDbks5t4JUbgaJpZM4UKxtO>
.
|
Yes! We've already moved a few core dependencies over, and it's gone quite well. It's just a lot of work is all. |
Thanks for raising the issue. Closing this as duplicate of googleapis/nodejs-datastore#9 |
@JustinBeckwith , why did you re-open this? |
We still have a dependency on request via gcs-resumable-upload. Can you post the results of a npm ls --production? |
Also worth posting a trace using require-so-slow now and from the 1.x release. |
Using GCS in Google Cloud Functions, the number of dependencies matters hugely in order to improve cold starts. I use GCS for one short upload (logging) and it seems like it is hurting my cold start times as it has over a hundred dependencies in total.
Are you folks caching your own packages for faster loading or not really?
The text was updated successfully, but these errors were encountered: