Webpack does everything Browserify does, but arguably if you&#x27;re used to both the configuration is marginally more transparent (although still terrible).  Also, arguably, new features tend to land in webpack a LITTLE earlier than browserify, which might be important to you in rare cases.<p>In short, I&#x27;ve used both, and I&#x27;m currently happy with webpack, and I have a decent configuration on my current project with a dev server, good production builds, support for CSS modules, and hot module replacement, all of which I could have in browserify.<p>Oh, webpack makes it a lot easier to dispense with gulp; my last browserify config was driven by gulp, but my current webpack config is just driven by a few lines of vanilla node.js code, which is kind of nice.<p>&gt; What part of my life would actually get better if I took the 4 hours of my life I will never get back to make this switch?<p>Probably none of them.  But if I had two boilerplate configs, one using gulp+browserify and the other webpack, I&#x27;d choose webpack because I think it&#x27;s VERY SLIGHTLY clearer and more maintainable.