gulp vs Parcel vs Webpack

Need advice about which tool to choose?Ask the StackShare community!

gulp

9.4K
6.6K
+ 1
1.7K
Parcel

454
167
+ 1
22
Webpack

24.1K
16.3K
+ 1
751
Decisions about gulp, Parcel, and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 0 upvote · 51.9K views
Why migrated?

I could define the next points why we have to migrate:

  • Decrease build time of our application. (It was the main cause).
  • Also jspm install takes much more time than npm 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.
See more

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.

See more
Pros of gulp
Pros of Parcel
Pros of Webpack
  • 452
    Build speed
  • 280
    Readable
  • 244
    Code-over-configuration
  • 210
    Open source
  • 175
    Node streams
  • 107
    Intuitive
  • 84
    Lots of plugins
  • 66
    Works great with browserify
  • 45
    Easy to Learn
  • 17
    Laravel-elixir
  • 4
    build workflow
  • 3
    Simple & flexible
  • 3
    Great community
  • 2
    jade intergration
  • 2
    Stylus intergration
  • 0
    Well documented
  • 0
    Clean Code
  • 8
    Easy setup
  • 8
    Zero configuration
  • 6
    Built-in dev server with livereload
  • 309
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 143
    Can handle all types of assets
  • 87
    Easy configuration
  • 20
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Webpack-Encore
  • 2
    Makes it easy to bundle static assets
  • 1
    Redundant
  • 1
    Better support in Browser Dev-Tools

Sign up to add or upvote prosMake informed product decisions

Cons of gulp
Cons of Parcel
Cons of Webpack
    Be the first to leave a con
    • 2
      Lack of documentation
    • 11
      Hard to configure
    • 2
      Spaghetti-Code out of the box
    • 2
      SystemJS integration is quite lackluster
    • 2
      Loader architecture is quite a mess (unreliable/buggy)
    • 2
      Fire and Forget mentality of Core-Developers
    • 2
      No clear direction

    Sign up to add or upvote consMake informed product decisions

    What is gulp?

    Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.

    What is Parcel?

    Parcel is a web application bundler, differentiated by its developer experience. It offers blazing fast performance utilizing multicore processing, and requires zero configuration.

    What is Webpack?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use gulp?
    What companies use Parcel?
    What companies use Webpack?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with gulp?
    What tools integrate with Parcel?
    What tools integrate with Webpack?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    What are some alternatives to gulp, Parcel, and Webpack?
    Grunt
    The less work you have to do when performing repetitive tasks like minification, compilation, unit testing, linting, etc, the easier your job becomes. After you've configured it, a task runner can do most of that mundane work for you—and your team—with basically zero effort.
    npm
    npm is the command-line interface to the npm ecosystem. It is battle-tested, surprisingly flexible, and used by hundreds of thousands of JavaScript developers every day.
    Yarn
    Yarn caches every package it downloads so it never needs to again. It also parallelizes operations to maximize resource utilization so install times are faster than ever.
    CodeKit
    Process Less, Sass, Stylus, Jade, Haml, Slim, CoffeeScript, Javascript, and Compass files automatically each time you save. Easily set options for each language.
    rollup
    It is a module bundler for JavaScript which compiles small pieces of code into something larger and more complex, such as a library or application. It uses the new standardized format for code modules included in the ES6 revision of JavaScript, instead of previous idiosyncratic solutions such as CommonJS and AMD.
    See all alternatives
    Interest over time
    News about Parcel
    More news