Visualize and analyze your React Native bundle to identify packages that increase its size.
react-native-bundle-visualizer is a command-line tool that analyzes and visualizes the contents of React Native application bundles. It helps developers identify which imported JavaScript libraries are contributing most to bundle size, enabling targeted optimizations to reduce load times and improve app performance.
React Native and Expo developers who need to optimize their app's bundle size, particularly those working on performance-sensitive mobile applications.
It provides a simple, integrated solution specifically for React Native's Metro bundler, offering visual insights that are directly actionable for reducing bundle bloat without requiring complex setup.
See what packages are increasing your react-native bundle size 📦
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly works with React Native's Metro bundler, providing accurate analysis by using source-map-explorer on Metro output, as stated in the purpose.
Supports both Expo projects (SDK 50+) and React Native CLI projects (0.72+), with a dedicated --expo flag for easy switching, covering major development workflows.
Generates HTML visualizations by default, offering interactive charts to pinpoint large libraries, making bundle optimization more intuitive, as shown in the animation.
Provides flexible arguments for platform, dev builds, entry files, and output formats (HTML, JSON, TSV), allowing tailored analysis for different scenarios.
Version 4.x requires Node.js 20+, forcing teams to upgrade and potentially breaking compatibility with older development environments, as noted in the compatibility table.
Exclusively designed for Metro bundler; it cannot analyze bundles from other bundlers like Webpack, limiting its utility in mixed or custom setups.
Users may encounter InvalidMappingColumn errors, requiring workarounds like --no-border-checks, indicating occasional reliability issues with source maps, as admitted in the FAQ.
Lacks built-in CI/CD integration or automated reporting, requiring manual command execution for each analysis, unlike some alternative tools with more automation.