Rolldown vs webpack

Rolldown is a free, open-source JavaScript bundler written in Rust and designed as the unified bundler powering Vite 8+. Its Rollup-compatible plugin API can reuse most existing Rollup plugins. Built-in capabilities include TypeScript and JSX transforms, syntax lowering, module resolution, ESM and CommonJS interoperability, define, inject, and minification. It can handle mixed ESM and CommonJS module graphs and supports configurable manual code splitting. Install commands are provided for npm, pnpm, yarn, bun, and vp. Prebuilt binaries are listed for Linux, Windows, Apple platforms, Android, and other targets; where none is distributed, a Wasm build or building from source are options. The guide recommends using Rolldown through Vite for most applications and points library authors to tsdown. Module types are experimental, and the JavaScript build() API may change in patch releases. The troubleshooting guide says Windows file-system access can slow builds, particularly when transforms run without plugins. An online REPL is linked, along with GitHub, Discord, and contribution resources. VoidZero Inc. holds the copyrights, funds development, and directs the project; it states Rolldown remains open source and MIT-licensed.

webpack is a free, open-source static module bundler for modern JavaScript applications. It builds a dependency graph and combines modules into bundles, with code splitting for on-demand loading. Built-in support covers JavaScript, JSON, WebAssembly, CSS and HTML. Loaders transform sources such as Sass into CSS or TypeScript into JavaScript, while plugins customize compilation through lifecycle hooks. ModuleFederationPlugin lets independently built applications share modules at runtime. Since version 4.0.0, webpack can run without a configuration file, although it remains highly configurable. Interfaces include the CLI, Node API, loader API and plugin API, and documentation covers integrations with Browserify, Brunch, Grunt, Gulp, Mocha and Karma. The project recommends local npm installation and a fresh Node.js installation; command-line use from webpack v4 onward also requires webpack-cli. The MIT-licensed software supports tree shaking and source maps. CSP is not enabled by default, and native CSS and HTML support are experimental.