Webpack bundle analysis: tracing indirect module dependencies

Module Inclusion Bottlenecks

When optimizing bundle sizes in webpack (version 5+), the performance configuration and webpack-bundle-analyzer can identify which modules are contributing to large asset sizes. However, determining the exact dependency chain that triggers the inclusion of a specific module remains complex when multiple indirect dependencies overlap.

The stats configuration provides raw JSON data regarding chunks and modules, but mapping a deeply nested dependency back to its original entry point or specific third-party package is not always intuitive during the analysis of a production build.

• How can the stats object be leveraged to isolate the specific dependency path causing a module to be bundled?
• Is there a documented method to differentiate between a module included via a direct import versus one pulled in by multiple overlapping indirect dependencies?