Products · Product
webpack
Raised as a usability problem by 79 people on Hacker News over 12 years (2015–2026), in 64 threads.
No issue was raised by at least 3 people in 3 threads this year.
- 1
- 2
Every issue, all time, most people first
Configuration is overly complicated for common use casesUnreviewed
20152026- Complicated configs take lots of time to get working2022-10-25
- Developers lose many hours to its complicated setup2022-05-27
- Config files are brittle and very hard to understand, requiring days of docs reading2021-11-16
Hard to learn, and it gets worse with heavy frameworksUnreviewed
20152026- Configuring Webpack was painful, with bespoke options across many tools2025-09-15
- Configuring webpack and tsconfig is confusing with poor docs, taking days to get right2024-05-04
- Configuring webpack for a project takes a day and no guide fits what they need2022-05-27
Every config change breaks something, so users dread touching itUnreviewed
20152026- Major upgrades are very hard, with arbitrary breaking changes and unclear documentation on where config goes2026-01-04
- Configuration is tedious and breaks with every version, so users cannot safely touch it2024-06-22
- Config is daunting, forgotten quickly, and dreaded each time it must be touched2020-10-11
Builds are much slower, needing workarounds or disabled featuresUnreviewed
20152026- Builds take 10-15+ minutes, and the stats.json output was malformed and opaque to debug2025-01-16
- Build is much slower, needs workarounds or disabled features to be usable2021-03-24
- Builds are slow to start and use only one core2020-12-24
Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.
The newest 50 complaints
- Major upgrades are very hard, with arbitrary breaking changes and unclear documentation on where config goes2026-01-04
- Configuring Webpack was painful, with bespoke options across many tools2025-09-15
- Builds take 10-15+ minutes, and the stats.json output was malformed and opaque to debug2025-01-16
- Configuration is tedious and breaks with every version, so users cannot safely touch it2024-06-22
- Configuring webpack and tsconfig is confusing with poor docs, taking days to get right2024-05-04
- Development build fills RAM until the laptop slows to a crawl and crashes2023-03-17
- Gets slow on complex projects2023-02-28
- Complicated configs take lots of time to get working2022-10-25
- Configuring webpack for a project takes a day and no guide fits what they need2022-05-27
- Developers lose many hours to its complicated setup2022-05-27
- Bundled code is eval-wrapped strings, so sourcemaps fail and debugging is impossible2022-01-13
- Commenter quotes a claim that webpack is so hard to understand that few people know it2022-01-04
- Config files are brittle and very hard to understand, requiring days of docs reading2021-11-16
- Spends days debugging frontend tooling, breaking changes and idiosyncratic configs2021-10-21
- Developers hated configuring it, so it needed heavy out-of-the-box setup2021-10-19
- Webpack became slow, bloated and confusing, as bad as the Gulp files it replaced2021-10-14
- Builds silently break with exit 0 after plugin upgrades, giving no error about the problem2021-10-14
- When builds break, fixing them takes developer days because few people understand its plugins2021-10-14
- Slow and hard for a first-time web developer to figure out2021-08-04
- Complex internals must be relearned every few months to remember how it works2021-04-28
- Config rarely works first time and error messages don't say what to fix2021-04-20
- Build is much slower, needs workarounds or disabled features to be usable2021-03-24
- Dynamic imports need reading 50 pages of confusing docs and a perfect config file2021-03-10
- Builds are slow to start and use only one core2020-12-24
- Builds of a small SPA take about 30 seconds and are hard to optimize2020-12-12
- Config is daunting, forgotten quickly, and dreaded each time it must be touched2020-10-11
- Hard to debug because its core behaviour is opaque and magical2020-10-10
- Generating CSS files needs extra plugins despite being advertised as a standard output2020-10-10
- Bundling a single file needs obscure config, and build failures give no clear error about what's broken2020-07-31
- Webpack is so badly designed that it signals problems across the whole JavaScript ecosystem2020-07-19
- Nested config options behave inconsistently across levels, so the author can't understand why things work2020-06-19
- Webpack is hard to learn, and it gets worse with heavy frameworks2020-06-09
- Requires hours of unnecessary configuration and fixes2020-05-26
- Setting up webpack for code splitting and CSS takes days of configuration2020-04-13
- Must mentally parse massive nested config objects to understand what it will do2020-01-10
- Hard to configure and has no sane defaults2020-01-05
- Many near-empty source files in browser; correct file hard to find for breakpoints2020-01-05
- Bootstrapping the build tooling is a time sink before doing anything useful2019-11-30
- Build does things automatically, so user can't tell what it does and debugging is hard2019-08-23
- Configuration is terrible and hard to get right2019-08-22
- Has to relearn Webpack configuration from scratch every time because it is hard to remember2019-05-29
- Webpack is sometimes difficult to configure, and its old docs were lackluster2019-04-01
- Config is so hard to get working that it takes days of trial and error2019-02-07
- Error messages don't point to trivial fixes, so hours are wasted searching for answers2019-01-02
- Broken source maps forced debugging multiple plugins instead of the app2018-12-03
- Found Webpack unintuitive, heavy and complex to work with2018-08-10
- Configuring it is verbose and complicated, and SplitChunks behaviour is opaque and undocumented2018-07-17
- Feature-rich, highly configurable tool is hard to learn and use2018-07-16
- Very difficult to understand and configure, few sane defaults, poor docs2018-07-16
- Slider resets to first slide when display area is resized, while bottom text stays unchanged2018-07-16