webpack is a static module bundler for JavaScript applications, created by Tobias Koppers and first released around 2012. Its job is to take an application’s source modules and their dependencies and combine them into one or more output bundles that a browser can load. By treating the application as a dependency graph built from a single entry point, webpack made it practical to write large front-end codebases as many small modules and ship them as optimized assets.
The webpack documentation organizes the tool around a handful of core concepts. An entry tells webpack which module begins the dependency graph, and an output configuration tells it where to emit the resulting bundles and how to name them. From those two ideas webpack walks the imports of the application and assembles everything it finds into the build.
The features that made webpack distinctive were loaders and plugins. Loaders transform non-JavaScript files into modules the bundler can include, so stylesheets, images, and other assets can be imported directly from JavaScript and processed through tools like babel during the build. Plugins hook into webpack’s build lifecycle to perform broader tasks such as bundle optimization, asset management, and injecting environment variables, giving the bundler an extensible architecture rather than a fixed pipeline.
webpack also popularized code splitting, the practice of breaking a single large bundle into multiple smaller chunks that load on demand. Instead of forcing users to download the entire application before anything renders, code splitting lets an app deliver only the code needed for the current view and fetch the rest later, which became a standard technique for keeping large single-page applications responsive.
Through the mid-2010s webpack became the default build tool for much of the JavaScript ecosystem, sitting underneath frameworks and starter kits that hid its configuration behind defaults. Its dependency-graph model and loader/plugin design shaped how later tools were understood, even as faster alternatives such as esbuild and Vite later challenged its position by rethinking how bundling and development servers should work.