Change8

Webpack

Dev Tools

A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.

Latest: v5.110.125 releases3 breaking changes4 common errorsView on GitHub

Release History

View all versions →
v5.110.13 fixes
15h ago

This patch release includes several bug fixes, including improvements to snapshot management, error handling for unparsable modules, and shorthand acceptance for optimization settings.

v5.110.04 fixes27 features
23h ago

This release introduces significant performance improvements through enhanced minification of CSS and HTML, better tree-shaking for CommonJS modules, and new performance hinting features. It also adds several new module rule conditions and presets, improving build flexibility and developer experience.

v5.109.25 fixes
Jul 28, 2026

This patch release for Webpack includes several bug fixes, including improvements to alias resolution, source map naming, and cache management. It also addresses issues with dead branch skipping and loader context reporting.

v5.109.17 fixes2 features
Jul 27, 2026

This release focuses on performance improvements across various webpack components, including parsers, stats generation, and plugins. It also includes bug fixes for improved compatibility with Deno and Bun, and enhancements to the persistent cache.

v5.109.033 features
Jul 23, 2026

This release introduces significant enhancements to built-in TypeScript, CSS, and HTML support, alongside improved CommonJS module handling and new output and experiment options. It also adds features for resource hints, build progress, and advanced HTML generation.

v5.108.42 fixes1 feature
Jul 4, 2026

This patch release focuses heavily on performance improvements across CSS and HTML parsing, reducing CPU and memory overhead. It also updates the default `output.globalObject` for universal targets.

v5.108.32 fixes
Jun 29, 2026

This patch release focuses on performance improvements in CSS parsing and memory usage, alongside fixes for Hot Module Replacement (HMR) codegen stability.

v5.108.22 fixes
Jun 29, 2026

This patch release addresses two specific issues: one related to lazy barrel deferral of side-effect imports and another concerning the handling of the 'node:' prefix for core modules used as externals.

v5.108.11 fix1 feature
Jun 26, 2026

This patch release includes a fix for property access issues with escaped namespace imports and enhances tracing capabilities for the ProfilingPlugin.

v5.108.0Breaking34 features
Jun 25, 2026

This release introduces significant enhancements for module resolution, targeting environments like Bun and Deno, alongside major improvements to tree-shaking, HTML module parsing, and runtime code generation using modern JavaScript features like `let`/`const`.

v5.107.26 fixes
May 25, 2026

This patch release focuses heavily on performance improvements, especially around watch mode rebuilds and context resolution overhead, alongside several fixes for caching, lazy compilation activation, and HTML asset hashing.

v5.107.1Breaking10 fixes6 features
May 21, 2026

This patch significantly improves HTML tokenization alignment with WHATWG specs and enhances tree-shaking for CommonJS bindings. It also fixes critical issues related to side-effect analysis stack overflows and source map generation coexistence.

v5.107.014 fixes13 features
May 20, 2026

This release introduces experimental TypeScript support via built-in Node.js features and significantly enhances CSS Modules capabilities, including scope hoisting support and improved source mapping/deduplication. New configuration options were added for controlling anonymous default export naming and HTML module extraction.

v5.106.22 fixes1 feature
Apr 15, 2026

This patch release fixes issues with default value handling in plugins and improves CSS @import inheritance, while migrating an internal dependency from mime-types to mime-db.

v5.106.13 fixes
Apr 10, 2026

This patch release addresses several regressions in ES5 environments related to default export naming and resolves issues with CSS module hashing and identifier renaming.

v5.106.013 fixes10 features
Apr 8, 2026

This release introduces new configuration options for CSS modules, VirtualUrlPlugin context support, and improved tree-shaking capabilities via CJS destructuring. Numerous bug fixes address issues across CSS processing, path resolution, and module generation.

v5.105.44 fixes1 feature
Mar 3, 2026

This patch release introduces a new method for source type inspection and includes several bug fixes related to expression handling, stats typing, CSS output, and export presence detection.

v5.105.3Breaking6 fixes3 features
Feb 26, 2026

This patch release focuses on bug fixes across context modules, HMR for CSS, entry point generation, and module resolution, while introducing stricter control over asset module side-effect marking via experimental flags.

v5.105.21 fix
Feb 12, 2026

This patch release addresses a regression in the WebpackPluginInstance type definition.

v5.105.13 fixes
Feb 10, 2026

This patch release focuses on improving compatibility and performance, notably fixing Windows filesystem issues in VirtualUrlPlugin and reverting a change related to `require("node:...")` compatibility.

v5.105.018 fixes7 features
Feb 3, 2026

This release introduces significant improvements to module resolution, especially around Workers and conditional imports, and adds configuration flexibility for TypeScript paths via the new tsconfig resolver option.

v5.104.12 fixes
Dec 18, 2025

This patch release addresses a security vulnerability in the HttpUriPlugin and fixes a runtime calculation bug related to Webpack import keys.

v5.104.08 fixes7 features
Dec 16, 2025

This release introduces several CSS module enhancements, new digest algorithms, and performance optimizations for dependency sorting and identifier parsing. It also includes critical security fixes for HttpUriPlugin to prevent SSRF and improves the stability of the webpack runtime.

v5.103.014 fixes11 features
Nov 18, 2025

This release introduces Dotenv and Manifest plugins, expands import.meta support, and adds new CSS export options. It also includes significant bug fixes for CSS modules, HMR, and TypeScript definitions.

v5.102.17 fixes2 features
Oct 7, 2025

This release focuses on bug fixes for worker imports, SystemJS compatibility, and CSS parsing, while adding support for browserslist environment extensions.

Common Errors

HookWebpackError2 reports

HookWebpackError in webpack usually indicates a problem during one of webpack's lifecycle hooks, often due to incorrect plugin configurations, missing dependencies, or file system access issues. To fix it, carefully review your webpack configuration, particularly loaders and plugins, ensuring they are correctly configured and that all required dependencies are installed; also verify that all file paths referenced in your configuration are valid and accessible.

WebpackInvocationError1 report

The "WebpackInvocationError", often featuring "Cannot read properties of undefined (reading 'tap')", typically arises from outdated or incompatible versions of webpack plugins or their dependencies. Ensure all webpack-related packages (webpack, webpack-cli, and all plugins) in your `package.json` are compatible and updated to their latest stable versions by running `npm install` or `yarn install` to regenerate your `node_modules` folder. If version conflicts persist, explicitly define compatible versions in your `package.json`.

SyntaxError1 report

A webpack "SyntaxError" often arises from using a loader (like ts-loader) incorrectly for a specific module type (like CommonJS), generating invalid syntax for that module system. To fix this, ensure your webpack configuration uses the correct loader options or test conditions to properly transform the code for the intended module type (e.g., setting `esModuleInterop: true` in `tsconfig.json` or adjusting `module.exports` statements). Also, verify no other loaders are conflicting and misinterpreting compatible code.

UnhandledSchemeError1 report

The "UnhandledSchemeError" in webpack usually means you're trying to import or require a resource with a protocol (like `node:`) that webpack doesn't know how to handle by default. To fix this, install and configure the `webpack-node-externals` plugin (or equivalent for other protocols) to tell webpack to treat these imports as external dependencies instead of trying to bundle them. Alternatively, use a plugin like `node-stdlib-browser` to polyfill node.js built-in modules for browser environments.

Related Dev Tools Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed