Feature: Configurable Module Bundler Selection (Webpack/Rspack/Vite)

[Abdel-Monaam-Aouini]

Goals

1. Add built-in support for switching between Webpack, Rspack, and Vite without experimental flags
2. rovide a standardized configuration API for all bundlers in next.config.js
3. Ensure consistent performance metrics and debugging experience across bundlers

Non-Goals

1. Creating custom bundler implementations or modifications
2. Supporting unofficial or community bundlers
3. Maintaining separate codebases for different bundlers

Background

Currently, Next.js primarily uses Webpack as its default bundler . This creates friction for teams wanting to use alternative bundlers in production, as experimental features may break or change. While there are community solutions and workarounds, having native, stable support for multiple bundlers would benefit the ecosystem.

The main alternatives currently available are:

1. Using experimental flags (unstable)
2. Custom webpack configurations (limited)
3. Community forks (fragmented ecosystem)
4. Manual bundler integration (high maintenance)

Proposal

Implementation through a new configuration option in next.config.js:

[Netail]

NextJS had some custom webpack plugins, which they then have to support for esbuild/rollup (Vite) too. RSpack could work as it's a drop-in replacement for Webpack, but as they are working on their own rust-based bundler, I doubt they'll add support for switching webpack compatible bundlers