-
Notifications
You must be signed in to change notification settings - Fork 63
I don't suppose there's a way to simply specify an array of methods you want? #76
Comments
Hi @faceyspacey! At that point you're probably better off manually cherry-picking. |
I am and all the package I use are (i.e. importing via full path, eg: https://www.dropbox.com/s/cik6rw9kmpexynr/Screenshot%202016-10-30%2016.54.44.png?dl=0 Is it that one of the packages I use imports via dot syntax? |
This plugin doesn't work with the per method packages like |
I know, I'm just trying to get it to 1kb since only like 5 methods are used. Going from a 150kb build (minified and gzipped) to 128kb build is substantial. ..Glad to know the the per method packages operate differently/separately. |
What are the 5 methods? |
memoize, debounce, find, findIndex, isEqual, isString, though webpack visualizer is picking up a few internal methods like _baseMergeDeep. here's what i'm using to visualize the size of imports: |
That build is 2.75 kB minified+gzipped. |
do you know why it's showing as so much more (yes, I know it's pre-minification/gzipping): https://www.dropbox.com/s/a4stwjrg4idxaiv/Screenshot%202016-10-30%2022.23.17.png?dl=0 The green bar without any orange child nodes, to me, has meant shipped but unused functions. Is it lodash core possibly? Does 70kb make sense for just that pre-minification/gzipping? |
If I had to guess it's probably showing the cumulative total of the individual uniminified modules before the |
Also, what about the babel plugin producing that list of methods and somehow passing it to the webpack plugin so that the lodash build is as tight as possible?
And if that's not possible, perhaps just leaving it on your file system for manually pasting it as a param to the webpack plugin, if that's the best we can do.
The text was updated successfully, but these errors were encountered: