Babel vs Browserify: What are the differences?
Babel and Browserify are both open source tools. It seems that Babel with 33.5K GitHub stars and 3.57K forks on GitHub has more adoption than Browserify with 12.7K GitHub stars and 1.12K GitHub forks.
SendGrid, Sentry, and Yahoo! are some of the popular companies that use Babel, whereas Browserify is used by Clever, Repro, and UNION. Babel has a broader approval, being mentioned in 888 company stacks & 661 developers stacks; compared to Browserify, which is listed in 111 company stacks and 42 developer stacks.
What is Babel?
What is Browserify?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Babel?
What are the cons of using Browserify?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Babel is awesome! 100% of the code for Cloudcraft.co is transpiled from ES2015 (even some ES7 extensions, like decorators and class properties!), using Gulp+Browserify for the frontend and on-the-fly translation in the Node.js backend. Babel allows us to use all the features of future JS, today, giving us a efficient and clean codebase. Overall, it has been an exceptionally smooth adoption, everything Just Works(tm), including debugging with source maps, etc.
When you are using modern (or sometimes experimental) features of the language, you’ll eventually have to transpile them so that your app works in a wide spectrum of user agents.
Babel is the transpilation tool of my choice.
Babel transpiles ES6/ES2015+ code to a format older browsers (*cough* IE *cough*) can understand. This allows developers to write modern JS code while remaining compatible with older systems.
Babel is used in Kuro (https://github.com/Marc3842h/kuro).
Kuro is the browser facing portion of shiro. We use Babel as a easy to use build system for our frontend stack.
It's the lesser of all of the other evils out there. Webpack makes you completely blind to how things are put together. I like gulp, this made it easy.
Main React functionality pipeline broken into CommonJS modules: Reflux data stores, React components (cjsx - coffee/jsx).
Made sharing node modules with the frontend real easy. Especially when developing hybrid apps.