Comparison
ChunkvsEntry point
Chunk
the build wrote out eleven numbered JavaScript files and the page only requests three of them.
One output file produced by the bundler, containing a subset of the module graph. Chunk boundaries decide what is downloaded when and what can be cached independently, so how the graph is cut matters more than how much of it there is. Too few chunks and every change invalidates everything; too many and you pay per-request overhead and lose compression efficiency.
Full entry →Entry point
you named the one file the build starts from and everything else was found by following its imports.
The module a bundler begins traversal from, and the root of one output bundle. A multi-page application has one per page; a single-page one usually has a single entry plus whatever code splitting produces. Adding an entry point duplicates any shared code into both outputs unless a shared chunk is configured, which is a common cause of a suspiciously large total.
Full entry →