Install webpack with Homebrew, apt, Nix

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• webpack
• webpack-cli

Project history

The public `webpack/webpack` repository was created on March 10, 2012. GitHub's ReadME Project recounts that Tobias Koppers created webpack while working on a master's thesis for web applications, beginning as an optimizer born from practical need and growing through collaboration with users.

webpack's core model is a static dependency graph. The official concepts documentation explains that webpack starts from one or more entry points, follows the modules an application needs, and combines them into bundles. That model fit the rise of CommonJS, AMD, ES modules, transpilation, CSS preprocessors, and single-page applications.

webpack 4, released in February 2018, lowered the barrier for common use by making a configuration file optional for simple bundles while preserving deep configurability. webpack 5 followed on October 10, 2020, with a major release focused on long-term caching, removals of deprecated behavior, new web-platform features, and development-experience improvements.

Adoption history

webpack spread because it solved several front-end problems at once: bundling JavaScript for browsers, code splitting for on-demand loading, asset processing through loaders, optimization through plugins, and a configurable build pipeline that frameworks could wrap. The ReadME Project characterized it as used by millions of developers around the world.

Its adoption was reinforced by the surrounding loader/plugin ecosystem and by framework tooling that hid or generated webpack configurations. Even as newer tools such as Rollup, Parcel, esbuild, Vite, and Turbopack changed developer expectations, webpack remained significant in long-lived applications, enterprise build systems, and projects relying on its mature plugin surface.

webpack 5's Module Federation gave the project a second adoption story beyond classic bundling. The webpack 5 release notes describe Module Federation as allowing multiple webpack builds to work together at runtime, enabling independently built code to behave like a connected module graph.

How it is used

Developers use webpack by defining entry points, output settings, loaders, plugins, and mode-specific behavior, usually in `webpack.config.js` for non-trivial projects. Since webpack 4, simple projects can run without an explicit config, but package maintainers still recognize the config file as the center of serious webpack setups.

Common usage patterns include compiling modern JavaScript and TypeScript for browsers, bundling CSS and images with content hashes, splitting code by route, running development servers with hot updates, and generating optimized production assets. In larger systems, webpack configuration often becomes shared infrastructure owned by platform or build-tooling teams.

Why package nerds care

webpack is package-nerd famous because it made `node_modules` and browser delivery collide at industrial scale. Its loader and plugin conventions shaped how npm packages advertise browser entry points, side effects, CSS handling, and asset behavior.

It is also a landmark in build-tool ergonomics: powerful enough to become the default, configurable enough to become notorious, and stable enough that newer tools are often explained by comparing what they simplify or replace from webpack-era workflows.

Timeline

• 2012-03-10: Public GitHub repository `webpack/webpack` created.
• 2012: Tobias Koppers began webpack while working on a master's thesis for web applications.
• 2018-02: webpack 4 released; configuration became optional for simple bundles.
• 2020-10-10: webpack 5.0.0 released.
• 2020: webpack 5 introduced Module Federation for connecting independently built webpack builds at runtime.
• 2026-07-02: The GitHub API showed continued activity on the `webpack/webpack` repository.

Related projects

• webpack is commonly discussed alongside Rollup, Parcel, Browserify, esbuild, Vite, Turbopack, Babel, TypeScript, and framework CLIs. Within webpack itself, webpack-cli, loaders, plugins, and Module Federation form much of the practical ecosystem.

Sources

• https://api.github.com/repos/webpack/webpack
• https://github.com/readme/podcast/masters-thesis-to-webpack
• https://github.com/webpack/webpack
• https://webpack.js.org/blog/2020-10-10-webpack-5-release/
• https://webpack.js.org/concepts/