Browserify vs Webpacker: What are the differences?
What is Browserify? Browser-side require() the node.js way. Browserify lets you require('modules') in the browser by bundling up all of your dependencies.
What is Webpacker? Use Webpack to manage app-like JavaScript modules in Rails (by Rails). Webpacker makes it easy to use the JavaScript preprocessor and bundler Webpack to manage application-like JavaScript in Rails. It coexists with the asset pipeline, as the purpose is only to use Webpack for app-like JavaScript, not images, css, or even JavaScript Sprinkles (that all continues to live in app/assets).
Browserify and Webpacker are primarily classified as "Front End Package Manager" and "JS Build Tools / JS Task Runners" tools respectively.
Browserify and Webpacker are both open source tools. Browserify with 12.8K GitHub stars and 1.12K forks on GitHub appears to be more popular than Webpacker with 4.29K GitHub stars and 893 GitHub forks.
According to the StackShare community, Browserify has a broader approval, being mentioned in 111 company stacks & 42 developers stacks; compared to Webpacker, which is listed in 7 company stacks and 5 developer stacks.