-
-
Notifications
You must be signed in to change notification settings - Fork 487
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
Incorrect total size in search result #251
Comments
Hmm are you sure your lodash in |
I think its a legit bug. I've overlooked this case. |
@th0r @valscion I think bug is here webpack-bundle-analyzer/client/store.js Line 153 in d7682a6
!module.groups before adding module size
|
@kyriiherman it's not so easy. What if the only found item is a directory? In your case the size will be zero. |
@th0r yes, this is correct behavior. in your case the directory is empty, otherwise all files inside directory are present in found modules, because files paths include directory name |
@kyriiherman No, it's not. You can input a regexp that will match only directory name e.g. |
@th0r oh, my fault( so we should check for |
I don't think it will work either. The proper solution would be to check nesting of the found items e.g. if we have found "lodash/find.js" module then we should ignore it's size if we also found a whole "lodash" directory. So this task is not so simple and may require quite significant changes in the data structure that currently represents modules tree. |
@th0r why you think solution with checking |
@kyriiherman |
@th0r so we need to filter modules tree in |
Yes the problem is still there. I don't know the answer to your other question, maybe someone else knows. |
Issue description
When I search for some modules total size isn't correct. It looks like total size is folder size + size of each file in folder
Technical info
Debug info
How do you use this module? As CLI utility or as plugin?
plugin
If plugin, what options were provided? (e.g.
new BundleAnalyzerPlugin({ analyzerMode: 'disabled', generateStatsFile: true })
){ openAnalyzer: false }
The text was updated successfully, but these errors were encountered: