Esbuild vs Rollup — why Vite uses both and when each is used

Vite strategically employs two different bundlers to optimize for the distinct requirements of development and production environments. This dual-bundler approach leverages the unique strengths of each tool where they excel best. esbuild, written in Go, provides unmatched speed for development-time operations like dependency pre-bundling and on-the-fly transpilation . Rollup, a mature JavaScript bundler, offers sophisticated chunk splitting, tree-shaking, and a rich plugin ecosystem essential for production optimization . The trade-off has been necessary because neither tool alone could optimally serve both development and production needs—until the introduction of Rolldown in Vite 8 .

The fundamental reason Vite uses both esbuild and Rollup lies in their complementary strengths and weaknesses. esbuild is blazingly fast and feature-rich, but its output, particularly regarding chunk splitting limitations, is not ideal for bundling applications . Rollup is mature and battle-tested for application bundling but is significantly slower than tools written in compile-to-native languages . Having to use two different bundlers creates suboptimal outcomes: subtle differences between development and production outputs can cause behavior inconsistencies, and user source code must be repeatedly parsed, transformed, and serialized by different tools throughout the production build, leading to avoidable overhead .

Rollup is exclusively used during the production build phase (vite build). Vite internally calls Rollup to handle module bundling, applying the configuration from vite.config.js (especially build.rollupOptions) to control the bundling process . Rollup's strengths that Vite leverages include sophisticated chunk splitting for optimal code organization, advanced tree-shaking to eliminate dead code, scope hoisting for improved runtime performance, and a mature plugin ecosystem that Vite can utilize during builds . The configuration sharing between Vite and Rollup means developers can directly influence Rollup's behavior through Vite's configuration file .

The dual-bundler architecture, while effective, introduced inconsistencies and overhead. To solve this, the Vite team built Rolldown, a next-generation bundler written in Rust . Vite 8 beta replaces the esbuild+Rollup combination with Rolldown as its single bundler. Rolldown matches esbuild's native-level performance (10-30× faster than Rollup) while maintaining Rollup-compatible APIs and plugin interfaces . Early adopters have seen dramatic improvements: Linear's production build times dropped from 46 seconds to 6 seconds, Ramp reduced build time by 57%, and Mercedes-Benz.io cut build time by up to 38% . This unification eliminates behavior differences between development and production, reduces redundant code processing, and enables advanced features like module-level persistent caching and Module Federation .