Webpack Stats Bundle Reviewer

How to use Webpack Stats Bundle Reviewer

Review actual selected Webpack 5 stats assets, chunk references and module source sizes while keeping emitted bytes separate. Find the largest supplied build assets and follow source chunk witnesses without uploading a stats file or executing a bundle. Nested concatenated modules remain explicit so their reported source sizes are not accidentally counted twice as emitted output.

1. Provide optional small webpack stats json, single-compilation webpack5 stats json.
2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
3. Copy the result or download a separate output; reset to clear the current form.

Good to know

• One UTF-8 JSON up to100,000 bytes,10,000 values and40 levels with an explicit Webpack 5 version string. Selected ungrouped assets only; MultiCompiler children and grouped asset rows are refused rather than flattened under an invented rule.
• At most500 unique asset names,500 chunks and2,000 module records with at most 20 nested module levels. Selected asset/module sizes use exact original nonnegative integer JSON values up to1 trillion; near-integer source spellings are not rounded into valid bytes.
• Emitted asset bytes are summed once per exact name and sorted by size. Module source estimates are separate; only root module records enter their own sum, nested records keep parent paths and are not added again. Neither total is gzip/Brotli/network-transfer/runtime-memory measurement.
• Selected chunk IDs are strings or exact safe integer source values within ±1 billion. Missing asset/chunk/module references remain diagnostics, at most 5,000. Hidden/filtered source can make this selection incomplete; no full build-success or runtime reachability verdict follows.
• Source errors/warnings, timings, sourcemaps, entrypoint budgets, compressed bytes and other bundlers are not assessed. Name/identifier values can contain private build paths and remain in this local report.
• Report text is at most 500,000 characters. Reduce source when a separate input/node/reference/output bound is exceeded.
• A same-origin module Worker loads its selected code, including the YAML writer for Dependabot, before ready within 10 seconds. A separate2-second computation deadline follows. Source is never evaluated, fetched, submitted, uploaded or automatically saved.
• Structured text output is limited to 500,000 characters. Reduce the supplied source when that separate output budget is exceeded.
• Inputs are processed on this device and are not automatically saved or uploaded.