Need advice about which tool to choose?Ask the StackShare community!
BrowserSync vs Webpack: What are the differences?
What is BrowserSync? Reload all your browsers, every time you hit save. BrowserSync makes your tweaking and testing faster by synchronising file changes and interactions across multiple devices. It’s wicked-fast and totally free.
What is Webpack? A bundler for javascript and friends. A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows to load parts for the application on demand. Through "loaders" modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
BrowserSync and Webpack are primarily classified as "Live Reloading" and "JS Build Tools / JS Task Runners" tools respectively.
BrowserSync and Webpack are both open source tools. Webpack with 49.8K GitHub stars and 6.27K forks on GitHub appears to be more popular than BrowserSync with 10.7K GitHub stars and 689 GitHub forks.
According to the StackShare community, Webpack has a broader approval, being mentioned in 2208 company stacks & 1341 developers stacks; compared to BrowserSync, which is listed in 10 company stacks and 12 developer stacks.
I could define the next points why we have to migrate:
- Decrease build time of our application. (It was the main cause).
- Also
jspm installtakes much more time thannpm install. - 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.
Pros of BrowserSync
Pros of Webpack
- Most powerful bundler308
- Built-in dev server with livereload181
- Can handle all types of assets142
- Easy configuration87
- Laravel-mix22
- Overengineered, Underdeveloped4
- Makes it easy to bundle static assets2
- Webpack-Encore2
- Redundant1
- Better support in Browser Dev-Tools1
Sign up to add or upvote prosMake informed product decisions
Cons of BrowserSync
Cons of Webpack
- Hard to configure15
- No clear direction5
- Spaghetti-Code out of the box2
- SystemJS integration is quite lackluster2
- Loader architecture is quite a mess (unreliable/buggy)2
- Fire and Forget mentality of Core-Developers2
Sign up to add or upvote consMake informed product decisions
What is BrowserSync?
What is Webpack?
Need advice about which tool to choose?Ask the StackShare community!
What companies use BrowserSync?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Webpack?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+31
+46
+39
+43+42+27