Getting into JavaScript Building & Bundling: Bundling Tools


Last updated:

This article aims to take a look at, and compare the different tooling choices available for JavaScript bundling.

This is the second part of my series about JavaScript bundling & building. If you haven’t read the first part yet, go check it out.

Bundling Tool Overview

Let’s start by taking a look at this table:

Supports CommonJSyesyesyes
Supports ES Modulesnoyesyes
Project Stars128755105016541
Project Contributors180546183
Project Commits/m *16344

Source: GitHub; 22.09.2019

(*) Commits from the 22.08 to the 22.09.2019

RequireJS was omitted because it is rarely used nowadays. Grunt and Gulp cover similar use cases to the tools listed above, but have been omitted due to not having bundling as their main goal.

Update 2021: A number of tools such as Snowpack, Parcel or esbuild have risen in popularity recently, but are not covered by this article.

Let’s take a closer look at the tools listed above, shall we?


With over 10000 Stars on Github, Browserify is the third largest bundling tool on the list. Browserify works as a command-line tool that supports the CommonJS syntax. One of the advantages of Browserify is the simple setup: no config files needed!
Dust run browserify with your input/output files.
Note that unlike the other tools in this list, browserify seems to usually be used in conjunction with tools like Gulp, because other common tasks like transpiling or minifying are not handled by it.


  • Quick and easy to use.


  • Only supports CommonJS.
  • Usually has to be used together with other build tooling.


Webpack is the biggest and most popular bundling system in the JavaScript ecosystem. Even though it can be a bit tricky to set up, once it gets running it is a very powerful bundling system that does not only support every popular module syntax, it can also be extended by all sorts of plugins that give webpack similar functionality to Grunt or Gulp powered build process. Not only can webpack build bundles, it also supports transpiling JavaScript through Babel or Typescript, as well as optimizing code via e.g. Terser. But webpack doesn’t stop at JavaScript: it also allows bundling of CSS, images and a lot more.
One thing that should be noted is that webpack tends to include some runtime code for module resolving in the final output, which might not be desired when bundling libraries.


  • Supports every popular module syntax.
  • Greatly customizable.
  • Can be used for pretty much everything a build process needs.
  • Huge community.


  • Configuration can be complex, especially with many plugins.


Rollup is the youngest of the bundler listed but grows at a steady rate nonetheless. Rollup specializes in ES modules but can support CommonJS as well. The plugins available for Rollup allow for a build process similar to webpack, with plugins for Babel or UglifyJS for example.
Unlike webpack, no runtime code for module resolving is injected which makes Rollup a good choice for libraries.


  • Supports every popular module syntax.
  • Greatly customizable.
  • Can be used for pretty much everything a build process needs.
  • Quick project growth.
  • Zero runtime overhead.


  • Smaller community than Webpack.


  • Browserify is for projects where you want to start quick and only use CommonJS, and/or projects which already have a build process involving e.g. Gulp.
  • Webpack if you want one beefy tool that can do everything very well, but can require more setup.
  • Rollup is similar to Webpack, but with less trouble setting it up in exchange for a slightly less mature ecosystem and a smaller community behind it.