Grunt vs Webpack: What are the differences?
Grunt and Webpack can be primarily classified as "JS Build Tools / JS Task Runners" tools.
"Configuration ", "Open source" and "Automation of minification and live reload" are the key factors why developers consider Grunt; whereas "Most powerful bundler", "Built-in dev server with livereload" and "Can handle all types of assets" are the primary reasons why Webpack is favored.
Grunt 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 Grunt with 11.9K GitHub stars and 1.55K GitHub forks.
Airbnb, Instagram, and Pinterest are some of the popular companies that use Webpack, whereas Grunt is used by Medium, Twitter, and Udemy. Webpack has a broader approval, being mentioned in 2206 company stacks & 1338 developers stacks; compared to Grunt, which is listed in 796 company stacks and 429 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.