rspack

Rspack does webpack's job in Rust. A bundler takes the hundreds of JavaScript files in your project and packs them into a handful the browser can load, and webpack has been the default for a decade. Rspack keeps webpack's config format and most of its plugin and loader ecosystem, so migration is often a config rename rather than a rewrite. MIT licensed, nothing gated.

The pitch is rebuild time. Rust plus incremental compilation keeps hot module replacement fast on large codebases, which is exactly where webpack starts to hurt. It comes from ByteDance's web infra team and anchors a wider toolchain: Rsbuild wraps it with defaults, Rspress builds docs sites. You install it from npm, so there is no ops burden.

Use it when you have a big webpack config you do not want to rewrite. Starting fresh, Vite is the more common default and Turbopack is Vercel's answer to the same problem. Compatibility is the reason to pick Rspack, not novelty.

The catch is that webpack compatibility is high, not total. Plugins that reach into webpack internals instead of its public hooks break, and Module Federation is where people usually get stuck. Check your plugin list before promising anyone a one day migration.