webpack
Shares rank 3 of 5 JavaScript bundlers by recommenders
Long-standing JavaScript bundler people recommend for its loader and plugin ecosystem and for handling complex or niche builds. Common caveat: complex configuration, slow builds and painful upgrades.
Long-standing JavaScript bundler people recommend for its loader and plugin ecosystem and for handling complex or niche builds. Common caveat: complex configuration, slow builds and painful upgrades.
55 people gave an opinion
- recommend it
- 13
- criticize it
- 42
- approval share
- 24%
Recommended in 7 of 13 months
- November 2025: not recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: recommended
- April 2026: not recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 13 people recommend itNeeds 10 or more, met.
- 0.3 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 7 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Easy setup, near zero-config now
“webpack config became easier compared to 2014/2015; I think they got to practically a zero-config by default.”
Comment from 4 Jun 2026 in “VoidZero Is Joining Cloudflare” “Webpack solved this problem with a few lines in the next.config.ts”
Comment from 26 Jan 2026 in “Turbopack: Building Faster by Building Less” Strong loader and plugin support
“We have good support for webpack loaders and have observed that that solves many (though not all usecases)”
Comment from 27 Jan 2026 in “Turbopack: Building Faster by Building Less” “Yarn, pnpm, webpack all have solutions for this”
Comment from 17 Mar 2026 in “Why Node.js needs a virtual file system” Handles niche needs via plugins
“for complex/niche use cases, you'll likely need webpack instead of whatever comes with Bun.”
Comment from 24 Jul 2026 in “Buz – A fork of Bun using modern Zig, with sub-1s incremental builds” “the answer for people who need basically any build plugin is "use the webpack mode"”
Comment from 26 Jan 2026 in “Turbopack: Building Faster by Building Less”
What people warn about
Each mark is one comment
Complex, heavy configuration
“you're bringing up webpack's complexity”
Comment from 13 Mar 2026 in “Vite 8.0 Is Out” “Wrangling a bunch of opinionated libraries and plumbing together systems with terrible ergonomics”
Comment from 2 Dec 2025 in “Codex, Opus, Gemini try to build Counter Strike” “today its kitchen sink and incredibly baroque configurations are as much a liability”
Comment from 9 Oct 2026 in “Cloudflare acquires Deno” - Comment from 26 Apr 2026 in “The West Forgot How to Make Things. Now It's Forgetting How to Code”
- Comment from 4 Jun 2026 in “VoidZero Is Joining Cloudflare”
Slow build performance
“The only regret is that it's a bit old and has performance issues.”
Comment from 5 Jan 2026 in “It's 2026 now. Is Webpack 6.x going to happen?” “waiting 50sec for a webpack build compared to 50ms with a Go toolchain is life changing”
Comment from 23 Feb 2026 in “The JavaScript Oxidation Compiler” Painful major version upgrades
“AI models aren't good with this (as evidenced by the hours I wanted trying to get any model to help me through a webpack4 to webpack5 upgrade.”
Comment from 14 Dec 2025 in “The Gorman Paradox: Where Are All the AI-Generated Apps?” “Upgrading eg Webpack and Babel and polyfill stacks and all that across multiple major versions is a serious mess.”
Comment from 22 Mar 2026 in “The Three Pillars of JavaScript Bloat” Adds dependency bloat
“Build systems (especially Babel and Webpack) were the first big culprits in terms of dependency bloat”
Comment from 23 Mar 2026 in “The Three Pillars of JavaScript Bloat” “never let us use Webpack 1.x because it depended on something that depended on something”
Comment from 17 Jun 2026 in “Why stdx is not on crates.io” “I also dislike things like webpack making every plugin an external dep”
Comment from 22 Mar 2026 in “The Three Pillars of JavaScript Bloat”
Other JavaScript bundlers people recommend
The four most recommended other JavaScript bundlers, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
See all 5 JavaScript bundlers, rankedWhat people said
40 of the 58 comments that mention it, newest first. Each links to the original comment.
“today its kitchen sink and incredibly baroque configurations are as much a liability”
“there was an issue, IIRC they weren't deterministic”
“nothing like 600mb of for type check server another 500 for webpack”
“Who wants to build something with webpack these days?”
“for complex/niche use cases, you'll likely need webpack instead of whatever comes with Bun.”
“Webpack should be discontinued by now, because Vite has replaced it in every way”
“Sure beats opening some ancient project and seeing some mix of Gulp, Grunt, webpack”
“never let us use Webpack 1.x because it depended on something that depended on something”
“webpack config became easier compared to 2014/2015; I think they got to practically a zero-config by default.”
“simplified the existing webpack thing drastically”
“Webpack - while maybe a win over Grunt/Gulp, was MASSIVELY complex.”
“the babel and webpack situation, which is truly kafkaesque”
“vite/webpack/rollup/rolldown”
“led to the creation of weird ecosystem like babel, webpack, eslint”
“I will never have to write another webpack.config.js as long as I live.”
“I configured freakin Gulp, Grunt, Brunch, Webpack 1 to 5”
“I'm on Node/webpack now and don't love where things are going.”
“Build systems (especially Babel and Webpack) were the first big culprits in terms of dependency bloat”
“Upgrading eg Webpack and Babel and polyfill stacks and all that across multiple major versions is a serious mess.”
“I also dislike things like webpack making every plugin an external dep”
“ancient Webpack with it's config split into 5 or so files”
“Yarn, pnpm, webpack all have solutions for this”
“800 lines config to compile code that's later interpreted is wild.”
“you're bringing up webpack's complexity”
“It look maybe two minutes on a decent developer desktop”
“an old webpack project with impenetrable plugin settings”
“Still easier than dealing with node dependencies, webpack and co, they make me wish”
“massive sets of packages pieced together with RequireJS or Rollup or WebPack or whatever”
“waiting 50sec for a webpack build compared to 50ms with a Go toolchain is life changing”
“without the burden of --- then very slow --- webpack”
“We have good support for webpack loaders and have observed that that solves many (though not all usecases)”
“Webpack solved this problem with a few lines in the next.config.ts”
“the answer for people who need basically any build plugin is "use the webpack mode"”
“as its builtin wasm parser (why was it parsing the binary anyway?) didn't recognize new opcodes”
“The only regret is that it's a bit old and has performance issues.”
“it's a huge generalist, and I think the specializing tools are showing their speed”
“AI models aren't good with this (as evidenced by the hours I wanted trying to get any model to help me through a webpack4 to webpack5 upgrade.”
“Webpack came out in late 2012 and took a few years to take over, thankfully.”
“anyone who actually measured it knew that bundlers just didn't deliver savings on that scale”
“Wrangling a bunch of opinionated libraries and plumbing together systems with terrible ergonomics”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.