45 engineers on Hacker News describe using Webpack first-hand: 8 endorse it, 10 regret it, 3 are mixed.
“we got tired of our 300+ line Webpack configs, so now the old days of server rendered HTML”
regret · production · ravenstine · 2022-07-20 · source ↗ · wrong label?“I've worked on projects with hundreds of thousands of LOC compiling with Webpack. Build time has literally never been a concern for me.”
endorse · production · ramesh31 · 2022-07-13 · source ↗ · wrong label?“we moved to NextJS (away from a Webpack config from 7 years ago) were: the handoff from server -> client is more seamless”
regret · production · 7 yr · drewpc · 2021-09-21 · source ↗ · wrong label?“faster builds, fewer dependencies, generally not having to worry about webpack at all”
regret · production · generalk · 2021-08-27 · source ↗ · wrong label?“the drop was a bit more than half the total time we had with Webpack in development”
regret · production · geoffharcourt · 2021-03-10 · source ↗ · wrong label?“my webpack.config.js file is 100 LoC total. This includes everything most projects probably need”
endorse · production · kingdomcome50 · 2021-02-04 · source ↗ · wrong label?“I've been using webpack since v1 and I can't recall having to open pull requests when periodically upgrading it”
mixed · production · JMTQp8lwXL · 2020-12-12 · source ↗ · wrong label?“Webpack 5+ on an SSD takes 5+ seconds to start things up... a ~30 second start up penalty in development is a killer”
regret · production · nickjj · 2020-12-07 · source ↗ · wrong label?“Webpack has been the most productive for me by far. We had a heck of a time with a couple of bundlers”
endorse · production · microcolonel · 2020-01-09 · source ↗ · wrong label?“I've either regretted it (babel/webpack/whatnot has screwed something up in prod that I didn't catch in dev)”
regret · production · zbentley · 2019-01-22 · source ↗ · wrong label?“especially bundling quirks with Webpack and NPM.”
regret · production · Tehnix · 2018-11-29 · source ↗ · wrong label?“It's messy, but it works. My biggest beef is that it's rather dissimilar from our production setup.”
mixed · production · skrebbel · 2018-11-05 · source ↗ · wrong label?“Honestly, Webpack was easier to use, simply because it is easier to find information on the web about it.”
endorse · personal · holtalanm · 2017-12-06 · source ↗ · wrong label?“We had a multi-MB page. Tree shaking got rid of most of it... Using webpack to chunk your site also reduces the payload to a manageable size.”
endorse · production · hajile · 2017-08-09 · source ↗ · wrong label?“one of the reason I avoid a lot of them is in my experience they can get in the way of maintainability”
regret · personal · alistproducer2 · 2016-12-18 · source ↗ · wrong label?“But its days to weeks to gain full understanding of those (Webpack is a slog)”
regret · production · mikeryan · 2016-11-16 · source ↗ · wrong label?“The breaking changes are a little bit painful (like the latest release), but using it in production and it is completely fine.”
mixed · production · DigitalSea · 2016-11-16 · source ↗ · wrong label?“I tried WebPack again and did it in an afternoon. That's when we switched.”
endorse · production · shados · 2016-11-02 · source ↗ · wrong label?“I regret wasting so much time ... setting up boilerplate dev environments file watchers transpilers hot module reload”
regret · production · borplk · 2016-10-11 · source ↗ · wrong label?“these modern javascript tools have solved a lot of problems we had.”
endorse · production · mehwoot · 2016-10-04 · source ↗ · wrong label?“I've been using React and Webpack to build the clientside of my Rails apps and have been very happy with that approach.”
endorse · personal · picardo · 2014-11-29 · source ↗ · wrong label?“then Webpack and React.”
neutral · production · erikpukinskis · 2023-11-11 · source ↗ · wrong label?“one still uses webpack because it uses the Monaco editor and we rely on certain plugins.”
neutral · production · josevalim · 2022-12-31 · source ↗ · wrong label?“I have things split out where the Webpack dev server runs in its own container only in development.”
neutral · personal · nickjj · 2021-12-07 · source ↗ · wrong label?“we switched from Webpack to esbuild earlier this year.”
neutral · production · Zarkaos · 2021-10-14 · source ↗ · wrong label?“But our actual Webpack typescript app is done locally.”
neutral · production · domlebo70 · 2020-08-13 · source ↗ · wrong label?“everything else is a Preact app so I spend most time on the Preact/Webpack stack.”
neutral · production · devmunchies · 2020-06-07 · source ↗ · wrong label?“use the Webpack loader css-loader/locals on the server so that it doesn't emit CSS files”
neutral · production · eliseumds · 2019-12-31 · source ↗ · wrong label?“Even compiling ~200kb of SCSS through a few Webpack loaders (inside of Docker with a volume) takes ~600ms”
neutral · production · nickjj · 2018-12-29 · source ↗ · wrong label?“running Dockerized web apps (mostly Flask, Rails and Phoenix apps with Webpack, etc.)”
neutral · production · nickjj · 2018-12-07 · source ↗ · wrong label?“Even the tools we use to make web parts now are React, Yeoman, webpack, Yarn, Sass etc.”
neutral · production · grumblepeet · 2018-12-04 · source ↗ · wrong label?“Would sometimes get a build to start failing with webpack where the require code was leaving stray references”
neutral · production · __s · 2018-08-27 · source ↗ · wrong label?“We migrated this approach from Sprockets to Gulp, and from Gulp to Webpack.”
neutral · production · demiazz · 2017-12-08 · source ↗ · wrong label?“there were some issues with getting customizations to the webpack build process since the CLI fork we used didn't allow for many changes”
neutral · production · fareesh · 2017-11-01 · source ↗ · wrong label?“my recent blog post on using the Cesium.js 3D globe library with Webpack and React”
neutral · personal · acemarke · 2017-03-23 · source ↗ · wrong label?“because webpack (what we use) moves all import statements to the top”
neutral · production · cygned · 2016-12-22 · source ↗ · wrong label?“found it easier to setup than Webpack's hmr.”
neutral · personal · petecoop · 2016-12-21 · source ↗ · wrong label?“There's `webpack.LoaderOptionsPlugin` which allows backwards compatibility, generally solves the problem.”
neutral · production · tonyhb · 2016-12-14 · source ↗ · wrong label?“using mostly the same tooling npm, babel (though with webpack on front end now)”
neutral · production · tracker1 · 2016-12-08 · source ↗ · wrong label?“There we use webpack-dev-server in proxy mode for easier development with livereload.”
neutral · production · alxeder · 2016-07-27 · source ↗ · wrong label?“we looked at jspm and switched to webpack.”
neutral · production · pdeva1 · 2016-02-02 · source ↗ · wrong label?“It's all basically a heavily commented webpack config and a few npm scripts.”
neutral · personal · TheAceOfHearts · 2015-07-08 · source ↗ · wrong label?“in our shop for various projects we use makefiles, shell scripts, rake and gulp/webpack”
neutral · production · mikekchar · 2015-07-01 · source ↗ · wrong label?“it's just a webpack config with a few flags per environment type, and to run every task you just use npm run-scripts.”
neutral · personal · TheAceOfHearts · 2015-06-21 · source ↗ · wrong label?