A Rollup plugin that visualizes and analyzes bundle composition to identify large modules and dependencies.
Rollup Plugin Visualizer is a build tool plugin that generates interactive visual reports of JavaScript bundle composition. It helps developers understand which modules are taking up space in their final output, enabling better optimization decisions by visualizing bundle structure and size.
Frontend developers and build engineers using Rollup, Vite, SvelteKit, or Rolldown who need to analyze and optimize their JavaScript bundles for performance.
Developers choose this plugin for its multiple interactive visualization templates (like sunburst, treemap, and network graphs) that provide actionable insights, along with privacy-conscious reports that only include statistical metadata, not source code.
📈⚖️ Visuallize your bundle
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Offers seven interactive views including sunburst, treemap, network, and flamegraph, allowing developers to analyze bundle composition from different angles for optimization insights.
Generates HTML reports containing only statistical metadata like file sizes and paths, not source code, ensuring data security and compliance with privacy concerns.
Seamlessly works with Rollup, Vite, SvelteKit, and Rolldown, as shown in the README with specific configuration examples for each tool.
Supports include and exclude filters using picomatch globs, enabling targeted analysis of specific bundles or files without clutter.
The README explicitly states that frontend report templates (e.g., network, treemap) can change without strict SemVer guarantees, potentially breaking visualizations in future updates.
Admits that network graphs can appear cluttered in real projects, requiring manual filtering of helper nodes like tslib or react to be usable, which adds overhead.
Features like using emitFile for SvelteKit or sourcemap integration require precise configuration and keeping the plugin last in the build chain, increasing setup complexity.