Open rtymchyk opened 5 years ago
Hi. Yes we have plans to lower bundle size and make it "tree-shakable"
Tree-shaking would definitely help. We only use the 'transform' functionality of the library, which I imagine is tiny in comparison to the rest of the source.
@rtymchyk does import { Client } from "filestack-js"
help?
@rtymchyk does
import { Client } from "filestack-js"
help?
No difference
@molszanski @pcholuj Hate to ping again, but is there anything scheduled for either trimming the size or just introducing tree shaking?
Notice in my screenshot below, it was 1.x.x, at 31kgb gzipped. At 2.0.5 (I'm using right now) it's 45kb gzipped. An upgrade to 3.18.0, I'm looking at almost 70kb gzipped. It's slowly creeping up and I'm using just a few tiny APIs from the library.
Yup, same here.
This is all I use:
import { Client } from "filestack-js"
this.client = new Client(conf.apiKey)
const rez = await this.client.upload(file, {}, s3StoreOptions)
const transoformUri = this.client.transform(originalFsHandle, transformation.filestackTransformOpts)
const meta = await this.client.metadata(uploaded.filestackHandle, {
width: true,
height: true,
md5: true,
mimetype: true,
})
Feel like writing my own client atm
Yup, same here.
This is all I use:
import { Client } from "filestack-js" this.client = new Client(conf.apiKey) const rez = await this.client.upload(file, {}, s3StoreOptions) const transoformUri = this.client.transform(originalFsHandle, transformation.filestackTransformOpts) const meta = await this.client.metadata(uploaded.filestackHandle, { width: true, height: true, md5: true, mimetype: true, })
Feel like writing my own client atm
Oops, sorry, for some reason I thought you were a maintainer here.
I'm using transform
and picker
. If it wasn't for the picker, I'd definitely just make my own utility :/
Hi we have plans to reduce sdk size, but it can take some time. Probably in 4.x.x it will be resolved
Hi we have plans to reduce sdk size, but it can take some time. Probably in 4.x.x it will be resolved
Thanks for the update!
Bundle size seems to be growing. We are considering switching to something else with less footprint
@pcholuj are there any updates on that? The bundle size is indeed concerning.
But no rush
Hi, sorry I`m no longer maintaining this repository.
@pcholuj thanks for letting us know. Does this mean the repository is no longer maintained or is it only you who is no longer maintaining it?
Are there any plans on optimizing size of the library? It's getting pretty inflated: