Massive Bundle Size about react-feature-toggles

[kennylavender]

@ericelliott I am sure it will lol, Il create some unit tests to make sure it works & keeps working 👍

[kennylavender]

@GodOfGrandeur thanks for the reminder, just created #211

[ericelliott]

I suppose we could use this, instead:

// Tiny, recursive autocurry
const curry = (
  f, arr = []
) => (...args) => (
  a => a.length === f.length ?
    f(...a) :
    curry(f, a)
)([...arr, ...args]);

But importing from lodash/fp/curry should not cause that kind of bloat. That's worth investigating deeper, and (if true) reporting to Lodash.

What are you using to bundle?

[GodOfGrandeur]

There's lots of blog posts about how lodash has massive bundle sizes. I'm not sure whats happening in this case but think the curry module is just badly packaged. I've attached a screenshot with it added to a standard create-react-app and source-map-explorer package added do the analysing.

Update: Seems to a issue with using the /fp/ version of the packages specifically.

[kennylavender]

I like the idea of using our own curry function so that we can avoid adding webpack/rollup. Looks like we are only using lodash in that one spot as well, so we can also remove lodash as a dependency.

[ericelliott]

@kennylavender LGTM. Does my autocurry spell work? It's very tiny. =)

[GodOfGrandeur]

@kennylavender thanks for looking at this, have you been able to get anywhere with this yet?

[kennylavender]

Published version 2.1.1 after #211

Bundle phobia now works:
https://bundlephobia.com/result?p=@paralleldrive/[email protected]

Size back down to 3.1kb from 47.36kb 👍