Babel vs Webpack: What are the differences?
Babel and Webpack are both open source tools. It seems that Webpack with 49.5K GitHub stars and 6.22K forks on GitHub has more adoption than Babel with 33.5K GitHub stars and 3.57K GitHub forks.
According to the StackShare community, Webpack has a broader approval, being mentioned in 2180 company stacks & 1297 developers stacks; compared to Babel, which is listed in 887 company stacks and 661 developer stacks.
I could define the next points why we have to migrate:
- Decrease build time of our application. (It was the main cause).
jspm installtakes much more time than
- Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.
We mostly use rollup to publish package onto NPM. For most all other use cases, we use the Meteor build tool (probably 99% of the time) for publishing packages. If you're using Node on FHIR you probably won't need to know rollup, unless you are somehow working on helping us publish front end user interface components using FHIR. That being said, we have been migrating away from Atmosphere package manager towards NPM. As we continue to migrate away, we may publish other NPM packages using rollup.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is Babel?
What is Webpack?
Need advice about which tool to choose?Ask the StackShare community!
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.
Webpack is the best bundler. Period.
Yes, it has a(n arguably) messy documentation, and a steep learning curve; but once you get the hang of it, there is nothing you cannot do with it.
Use it and you don’t have to use any other bundler at all.
It has a vivid ecosystem, and great plugin support.
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.
My preferred build tool; allows me to bundle my JSX, JS, CSS files for easy access and I can pass the bundle through my node server for server side rendering.
Flexible building and compiling of source for browser consumption, mainly for JS, but experimenting a little with CSS (although I prefer StylusJS for CSS).
We use this to optimise the delivery of the client-side for our revised Admin System, so it's able to be delivered to browsers as efficiently as possible.