webpack: build tool and module bundler

What it is

Webpack builds a dependency graph from JavaScript and related assets, transforms them through loaders, and emits production bundles through a highly extensible plugin system. It can shape almost every stage of a front-end build, which is both the selling point and the warning label.

Best for

Webpack remains a strong choice for large or long-lived applications with mixed assets, custom compilation requirements, established plugins and enough existing configuration that “replace the bundler” is really an architecture programme wearing trainers.

Avoid it if

For a new application with ordinary requirements, Vite, Parcel or a framework-owned build may provide a much shorter path. Webpack can start without configuration, but its advantage appears when you need control. If you do not, you are maintaining optional complexity.

Current state

Webpack 5.109.2 shipped on 28 July 2026. The current official getting-started path uses webpack-cli 7, which requires Node.js 20.9 or newer and webpack 5.101 or newer. The maintained 5.x line continues adding ESM, CSS and cache improvements rather than waiting ceremonially for Webpack 6.

Alternatives

Vite optimises the development loop and uses Rollup for production. esbuild and Rspack pursue speed with different compatibility trade-offs. Parcel favours convention and low setup. Rollup remains particularly attractive for libraries. Existing Webpack estates should compare migration cost, not benchmark screenshots alone.

Why it belongs

It belongs because maturity is a feature. Webpack has accumulated answers for awkward assets, old browsers, unusual targets and enterprise build graphs that newer tools may encounter only after the launch post.

Get started

• Use Node.js 20.9 or newer for the current CLI.
• Install locally: npm install --save-dev webpack webpack-cli.
• Begin with one entry and production build. Add loaders and plugins only for requirements you can name.