Webpack, the widely adopted JavaScript module bundler maintained under the OpenJS Foundation, has published its 2026 roadmap, outlining a comprehensive set of improvements focused on reducing plugin dependencies, expanding runtime compatibility, and laying the groundwork for webpack 6.
The roadmap, authored by Technical Steering Committee member Even Stensberg, introduces several priorities, including native CSS module support without plugins, a new universal compilation target, built-in TypeScript transpilation, and HTML entry point integration. The roadmap also signals webpack’s intent to explore performance optimizations inspired by competitor tools.
One of the most significant changes is the move to integrate CSS module support directly into webpack’s core. Currently available behind the experimental.css option, this feature eliminates the need for mini-css-extract-plugin. The team expects to complete integration into core around early 2026, with the feature remaining experimental until webpack 6, at which point plugin-based CSS handling will no longer be necessary. Developers can enable the experimental support today.
Another headline item is the proposed universal target, designed to compile code that runs across Node.js, Bun, Deno, and browser environments. Regardless of whether an application uses CommonJS modules, webpack will wrap them so that the resulting output is pure ESM, making it runtime-agnostic. ESM output is not fully complete yet, with additional fixes and missing tests still required.
The roadmap also announces plans for built-in TypeScript support, removing the need for ts-loader, and native HTML entry points, removing the dependency on html-webpack-plugin. Both of these follow the same pattern of absorbing common plugin functionality into core. Additionally, the team is evaluating a lazy barrel optimization, inspired by Rspack, that skips building unused re-exported modules in side-effect-free barrel files until they are actually needed. Other improvements include a unified minimizer-webpack-plugin to replace the current collection of separate minimizers such as terser-webpack-plugin and css-minimizer-webpack-plugin, and an exploration of a core Multithreading API to bring better parallel processing to large builds.
In terms of competitors, the bundler landscape has shifted considerably. Vite has become the default choice for many new projects, and Rspack, a Rust-based webpack-compatible alternative from ByteDance, offers significantly faster builds while maintaining compatibility with most webpack plugins. One user on Hacker News raised an interesting point about governance, noting that webpack’s position under the OpenJS Foundation provides neutrality that VC-backed alternatives may not, stating concerns about the ecosystem getting vertically integrated under a single commercial roadmap.
On Reddit, sentiment was mixed, with one user noting they would “welcome a revival” but suggesting that short of a Rust/Go rewrite they’re going to have a hard time of it.
A lot of commenters suggested that the propsed changes are ‘too late’:
They’ve fallen too far behind to still be competitive now.
I can literally build projects in less than a second with Rolldown-Vite that used to take nearly a minute with Webpack.
A webpack maintainer responded on the thread, clarifying:
We aren’t aiming to compete with other bundlers, we just want to modernize webpack, make it faster wherever possible, and give it some fresh air. Use the tool you think works best for you. But we known still many use webpack, and for that, we aim to make their experience even friendlier and better, keeping the stability we’re known for.
For teams looking to stay current, webpack provides an official migration guide for upgrading from version 4 to version 5, alongside a detailed changelog. Teams considering alternatives can also reference Rspack’s migration documentation, which is designed for webpack 5 projects looking for a drop-in performance improvement.
Webpack is an open-source module bundler for JavaScript applications, originally created by Tobias Koppers. It processes and bundles assets including JavaScript, CSS, and images, and remains one of the most widely installed build tools in the npm ecosystem, with first-class integration across frameworks such as React, Angular, and Vue.
