Comparison
Duplicate dependencyvsModule graph
Duplicate dependency
two copies of the same library ended up in the bundle because two packages asked for different versions.
The same package appearing more than once in the output because the version ranges could not be deduplicated. It doubles the bytes and, for anything holding module-level state, breaks it outright — two copies of a framework or a context mean instances that cannot see each other. This is why 'invalid hook call' and 'context is undefined' are so often really a resolution problem.
Full entry →Module graph
you imported one helper and the build pulled in a date library you have never used directly.
The directed graph of every module reachable from the entry points, which is the exact set the bundler must account for. Bundle size is a property of this graph rather than of your own code, so one transitive import can dominate the output. Reading it is the first step of every size investigation, which is what a bundle analyser is for.
Full entry →