JavaScript Bundle Composition Viewer
Inspect supported build manifests; compare module weights and shared dependencies.
Inspect esbuild metafile module weights, output reconciliation, shared-chunk membership and declared imports. No code is run and byte counts are not runtime or compressed-transfer costs.
Using JavaScript Bundle Composition Viewer
Inspect supported build manifests; compare module weights and shared dependencies.
- Try the tailored worked example, or open supported local sources. Configuration-only builders start from editable settings. Input schema: Supported input is an esbuild metafile with inputs, outputs and bytesInOutput attribution.
- Select a Review card for source evidence and supported manual fields. Details & settings controls the thresholds, patterns, URL policy or observation windows; originals stay unchanged.
- Use Preview to inspect the result and method notes. Interactive accessibility prototypes support real keyboard controls; search tools work only with supplied evidence.
- Use Export for the complete workflow ZIP or individual artifacts. Open an exported file before publishing it. Save review retains settings/decisions and source fingerprints; file-based projects need the exact originals to reopen.
Example
The worked example is specific to JavaScript Bundle Composition Viewer. It uses Supported input is an esbuild metafile with inputs, outputs and bytesInOutput attribution. Inspect esbuild metafile module weights, output reconciliation, shared-chunk membership and declared imports. No code is run and byte counts are not runtime or compressed-transfer costs.
Questions & answers
What does JavaScript Bundle Composition Viewer support?
Inspect esbuild metafile module weights, output reconciliation, shared-chunk membership and declared imports. No code is run and byte counts are not runtime or compressed-transfer costs.
What should my input contain?
Supported input is an esbuild metafile with inputs, outputs and bytesInOutput attribution.
What can I export, and does this change my live website?
Exports include the result data, source fingerprints, decisions and task-specific artifacts such as printable HTML, SVG review evidence, timed VTT notes, JSON-LD, sitemap XML, rule cases or checklists. These pages do not deploy rules, submit URLs, crawl a server or publish content. Public pages retain approved ads and optional consent-based analytics.
What should I verify before relying on the result?
Use the method notes and full evidence. Files are normally limited to eight sources, 25 MiB each and 80 MiB total, with smaller format/graph/image bounds. Worker analyses stop after 30 seconds. Accessibility helpers require real user/assistive-technology review; search evidence cannot guarantee indexing, eligibility, ranking changes or causal effects.
Related tools
A useful next step for your task.
Developer & DataHAR Network AnalyzerInspect a local HAR capture with request filters, timing waterfalls, status and domain summaries, request details, CSV exports and a minimized…
Developer & DataWeb App Manifest InspectorReview web-app names, start URLs, scopes, icons and display settings with resolved paths.
Developer & DataCanonical Conflict AnalyzerCompare canonical, redirect and sitemap signals from imported crawls; export contradictions.
Developer & DataIndexability Decision TraceCombine supplied robots, meta and status evidence; explain likely indexability barriers.
Help improve this tool
Report a problem or suggest an improvement
Describe the issue without pasting private tool input. Feedback goes to our admin inbox.