# webpack

13 Hacker News commenters recommended webpack and 42 criticized it, November 2025 to November 2026. It was recommended in 7 of 13 months.

**Verdict:** 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.

## Why people recommend it

- Easy setup, near zero-config now (2 comments): "webpack config became easier compared to 2014/2015; I think they got to practically a zero-config by default." ([source](https://news.ycombinator.com/item?id=48400402)) "Webpack solved this problem with a few lines in the next.config.ts" ([source](https://news.ycombinator.com/item?id=46761534))
- Strong loader and plugin support (2 comments): "We have good support for webpack loaders and have observed that that solves many (though not all usecases)" ([source](https://news.ycombinator.com/item?id=46784408)) "Yarn, pnpm, webpack all have solutions for this" ([source](https://news.ycombinator.com/item?id=47414770))
- Handles niche needs via plugins (2 comments): "for complex/niche use cases, you'll likely need webpack instead of whatever comes with Bun." ([source](https://news.ycombinator.com/item?id=49040868)) "the answer for people who need basically any build plugin is "use the webpack mode"" ([source](https://news.ycombinator.com/item?id=46761392))

## What people warn about

- Complex, heavy configuration (5 comments): "you're bringing up webpack's complexity" ([source](https://news.ycombinator.com/item?id=47361924)) "Wrangling a bunch of opinionated libraries and plumbing together systems with terrible ergonomics" ([source](https://news.ycombinator.com/item?id=46122726)) "today its kitchen sink and incredibly baroque configurations are as much a liability" ([source](https://news.ycombinator.com/item?id=50022748))
- Slow build performance (2 comments): "The only regret is that it's a bit old and has performance issues." ([source](https://news.ycombinator.com/item?id=46495076)) "waiting 50sec for a webpack build compared to 50ms with a Go toolchain is life changing" ([source](https://news.ycombinator.com/item?id=47120293))
- Painful major version upgrades (2 comments): "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." ([source](https://news.ycombinator.com/item?id=46263422)) "Upgrading eg Webpack and Babel and polyfill stacks and all that across multiple major versions is a serious mess." ([source](https://news.ycombinator.com/item?id=47476182))
- Adds dependency bloat (3 comments): "Build systems (especially Babel and Webpack) were the first big culprits in terms of dependency bloat" ([source](https://news.ycombinator.com/item?id=47493535)) "never let us use Webpack 1.x because it depended on something that depended on something" ([source](https://news.ycombinator.com/item?id=48571676)) "I also dislike things like webpack making every plugin an external dep" ([source](https://news.ycombinator.com/item?id=47475028))

## Alternatives hackers recommend

- [Vite](https://hackerapproved.com/p/vite.md): 135 recommend
- [esbuild](https://hackerapproved.com/p/esbuild.md): 31 recommend
- [Rolldown](https://hackerapproved.com/p/rolldown.md): 13 recommend
- [Turbopack](https://hackerapproved.com/p/turbopack.md): 12 recommend

## Cite as

Hacker Approved, "webpack", https://hackerapproved.com/p/webpack/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).