Not all packages showing up in results - possibly related to webpack code splitting

[jharris4]

I've been using webpack-bundle-size-analyzer for a while now, and it's been working great.

I have however recently noticed that some packages are not showing up anywhere in my analyzer results. I'm fairly certain this is related to the fact that I recently started using code-splitting with webpack (https://webpack.github.io/docs/code-splitting.html)

For example, I have a reports page that when accessed, dynamically loads a bundle which uses the d3.js npm package to show some charts, yet d3.js is not showing up anywhere in the analyzer results. If I add an import of d3.js to my main bundle, it starts showing up in the analyzer results again.

Any advice on how to resolve this would be greatly appreciated. I've checked the output from webpack -p --json and I am seeing d3.js mentioned when it's loaded in the code-split bundle. I can provide more specific info / snippets from the webpack json output etc. if that helps.

[robertknight]

Thanks for the report @jharris4 - If you could try to boil the problem down to a minimal test case that would be very helpful.

[jharris4]

Interesting, I just created a stripped down test case with code splitting, and the analysis seems to be working correctly ever for the code split bundles.

There are quite a few dependencies in my project (which unfortunately I cannot share since it contains proprietary code), so I'm now wondering if the cause is related to one of those dependencies, or perhaps it's related to the large number of dependencies...

Do you think the issue can be pinpointed by examining the output of webpack -p --json? If so, I could spend some time scrubbing proprietary content from the output and posting it...