3 ms·
> The only reason I tolerate webpack is because of how convoluted the front end web build chain has become. I've moved back to browserify (/ watchify) for hobb
by josephg 9y ago
> The only reason I tolerate webpack is because of how convoluted the front end web build chain has become.
I've moved back to browserify (/ watchify) for hobby web projects and I've been very happy with it. Its a huge relief to jettison all the complexity that webpack brings. Browserify configuration often fits on the command line even for complicated projects. You have great tools for analysing bundle size with disc[1], and you can do hot reloading on SPAs with budo[2]. The ecosystem has babelify for JSX, tsify for typescript, uglifyify + unassertify for minification, and sheetify for CSS.
Browserify also seems way faster. I haven't tried webpack 4, but with webpack 3 I've had plenty of builds that take nearly a minute. Its out of control.
Webpack seems like the web generation's automake & autoconf. How long before we have tools which generate webpack configuration programatically, and which need configuration themselves.
[1] https://www.npmjs.com/package/disc https://www.npmjs.com/package/disc
[2] https://www.npmjs.com/package/budo https://www.npmjs.com/package/budo
- navs 9y agoI recently made the switch to using ParcelJS [1]. Came from a browserify + rework + npm run scripts setup and wanted something with 0 configuration for my projects. Parcel's been that for me. Disclaimer: I'm not a serious webapp developer/software engineer. I mostly build websites so mileage may vary. [1] https://parceljs.org/ https://parceljs.org/
- onion2k 9y agoWebpack 4.0 also has zero config and it works exceptionally well.
- fiatjaf 9y agoEven better than watchify is the combo entr + browserify-incremental.
- mattdesl 9y agoGlad you are enjoying budo! It's a little tool that I built before Webpack became so popular, yet I'm still finding myself using it daily for the last couple years. I'm actually working on some new tools that combines my favourite parts of budo, webpack, babebl, and parcel... But ultimately with very similar usage and "unix philosophy" approach as the rest of browserify. :)
- jekrb 9y agoI also feel like browserify resonates better with me. I use the browserify plugin "tinyify" to make the final output smaller: https://github.com/browserify/tinyify https://github.com/browserify/tinyify If I'm working on a choo app I use banaki which uses browserify and my preferred bundle optimization plugins/transforms under the hood: https://github.com/choojs/bankai https://github.com/choojs/bankai
- dabernathy89 9y ago> How long before we have tools which generate webpack configuration programatically, and which need configuration themselves. Haha, too late! I actually really enjoy using Laravel Mix, which despite the name is not tied to Laravel. It's a Webpack wrapper that simplifies it significantly for many common use cases. https://github.com/JeffreyWay/laravel-mix https://github.com/JeffreyWay/laravel-mix
- neovive 9y agoMix is great! Webpack is very powerful and complex, but 90% of the time I just need to compile CSS/Sass and ES6 Modules. For these common scenarios, Mix makes this super-simple without having to dig into the Webpack config. If you stick with the very sensible defaults, your config can be as simple as: mix.js('resources/assets/js/app.js', 'public/js') .sass('resources/assets/sass/app.scss', 'public/css'); Here are the docs: https://laravel.com/docs/5.6/mix https://laravel.com/docs/5.6/mix