Making front end modules actually work
summary
Compares Webpack and Browserify by showing concrete trade-offs: dependency graphs become explicit and bundling produces one JS file; webpack loaders run at the app root while browserify transforms live in package.json; CSS and images can be bundled (URL/file loaders, css loader + style loader) and CSS local modules provide per-component class names; libraries/output externals let a bundle exclude React and target multiple consumers; demos and config snippets prove which approaches actually build reusable artifacts and which break cohesion.
AI-written summary · about
chapters (4)
related talks
18mFront End Dependency Management
36mUnbundling the JavaScript module bundler
30mPackWars: Webpack vs Browserify vs SystemJS vs require.js
26mA tale of two front-end development environments: or how bend npm3 to your will
30mExcuse Me, I Have to Assemble the Frontend
45mMicro Frontends in Action!
34mGift Wrap Your Code with Webpack
27mThe future of frontend tooling