Webpack bundle analysis: tracing indirect module dependencies

Answer the core question

To isolate the exact dependency chain that pulls a module into a bundle you can rely on two parts of the stats JSON:

• module.issuer – the single module that imported the current one.
• moduleGraph (when stats.moduleGraph: true) – lists all parents and children for every module.

By walking the issuer chain from the target module back to an entry point you reconstruct the full import path. When a module has multiple parents in moduleGraph, it is being shared by several indirect dependencies.

Confirmed facts

• The issuer field is present for every module that was imported by another module.
• Modules that are entry points or that webpack could not resolve an importer for have no issuer.
• The reason array contains the exact import statement that caused the module to be added, and duplicates indicate multiple import paths.
• When moduleGraph is enabled, each node’s parents array shows all modules that import it, allowing you to spot overlapping indirect dependencies.

Practical steps for this case

1. Generate the stats file with module graph:

   webpack --config webpack.config.js --json --profile --generateStatsFile --stats.moduleGraph true > stats.json
   

2. Load the JSON in Node.js:

   const fs = require('fs');
   const stats = JSON.parse(fs.readFileSync('stats.json', 'utf8'));
   const targetId = 'path/to/your/target/module.js'; // replace with actual identifier
   const target = stats.modules.find(m => m.identifier === targetId);
   

3. Walk the issuer chain:

   let chain = [];
   let current = target;
   while (current) {
     chain.push(current.identifier);
     if (!current.issuer) break; // reached an entry point
     current = stats.modules.find(m => m.identifier === current.issuer);
   }
   console.log('Import path:', chain.reverse().join(' > '));
   

4. Inspect overlapping parents:

   const node = stats.moduleGraph.nodes.find(n => n.identifier === targetId);
   if (node.parents.length > 1) {
     console.log('Shared by:', node.parents.map(p => p.identifier));
   }
   

5. Cross‑check with source files: Open the listed identifiers in your editor to verify the import statements match the reason entries.

What to ask for next

To refine the recommendation, could you provide the identifier of the module you want to trace (or its path relative to the project root)? This lets the script locate the exact node in the stats file.