Modesto  Corwin

Modesto Corwin


Webpack, Rollup and Parcel Compared

Let’s build a React app using Webpack, Rollup and Parcel to compare these three bundlers.


#webpack #parcel

What is GEEK

Buddha Community

Webpack, Rollup and Parcel Compared
Meggie  Flatley

Meggie Flatley


Benchmarking Bundlers 2020: Rollup vs. Parcel vs. Webpack

Bundlers serve as a cornerstone technology for all modern web apps. We’ve benchmarked Rollup, Parcel.js, and webpack across multiple criteria.

Bundlers serve as a cornerstone technology for all modern web apps — or, more specifically, all JavaScript apps. As the frontend world progressed with more client-side-rendered apps, ideas began to emerge about how to efficiently bundle our tons of JS.

Cognitively, as the number of options increase, selection becomes difficult. Here, we will analyze the tech and non-tech competencies of the top bundlers available today to make your decision easy and well informed.

We’ll be covering:

For comparing technical competencies, we have picked up React Facebook Pixel as a library and a very basic React app as a sample to benchmark each of these bundlers.

This comparison is not to establish a single winner from amongst these great tools; rather, it is to help you more easily make your decision. All of these bundlers are definitely great tools managed by great people, and they are all super awesome in one way or another. To all the maintainers, contributors, sponsors, and backers, cheers


Configuring a bundle has been one of the most cursed yet most sophisticated areas in the frontend world. For small-scale applications, one might feel this should be very straightforward. Still, as the application’s size grows, we need more sophisticated configurations to keep our apps efficient and performant.

We have witnessed many debates among developers about how tedious it is to configure a modern-day tech stack for a small app. These debates and the common patterns subsequently adopted by a majority of the community have led many bundlers to offer zero-config solutions.

Though it’s claimed by almost all of these bundlers, being zero-config is not possible for any of them. It is more about being quickly configurable and keeping the configuration guides as comfortable as possible.

All of these bundlers have their reds and blues in this area. Here, we are sharing configs for generating distribution packages for React Facebook Pixel. It will give you a glimpse of how it looks like for each of these bundlers.


const path = require('path');
const TerserPlugin = require('terser-webpack-plugin');

module.exports = {
  entry: ['./src/index.js'],
  output: {
    path: path.join(__dirname, 'dist'),
    filename: 'fb-pixel-webpack.js',
    libraryTarget: 'umd',
    library: 'ReactPixel',
  module: {
    rules: [
        use: 'babel-loader',
        test: /\.js$/,
        exclude: /node_modules/,
  resolve: {
    extensions: ['.js'],
  optimization: {
    minimize: true,
    minimizer: [
      new TerserPlugin({
        terserOptions: {
          warnings: false,
          compress: {
            comparisons: false,
          parse: {},
          mangle: true,
          output: {
            comments: false,
            ascii_only: true,
        parallel: true,
        cache: true,
        sourceMap: true,
    nodeEnv: 'production',
    sideEffects: true,


import babel from '@rollup/plugin-babel';
import { nodeResolve } from '@rollup/plugin-node-resolve';
import { terser } from 'rollup-plugin-terser';
import filesize from 'rollup-plugin-filesize';
import progress from 'rollup-plugin-progress';
import visualizer from 'rollup-plugin-visualizer';

export default {
  input: 'src/index.js',
  output: [
      file: 'dist/fb-pixel.js',
      format: 'cjs',
      name: 'ReactPixel',
      exports: 'named',
  plugins: [
    babel({ babelHelpers: 'bundled' }),
    // All of following are just for beautification, not required for bundling purpose


We didn’t need any configs for Parcel, as the default configs were enough to handle our library. Here is the command we used:

    "bundle:parcel": "parcel build src/index.js --experimental-scope-hoisting --out-file fb-pixel-parcel.js",

Here is my conclusion for this:

  • webpack still requires us to use ES5 syntax, which makes it a little problematic
  • Rollup has simpler syntax and looks ideal for managing libraries
  • Parcel v2 is coming up with configuration file support with awesome default configs to extend for sophisticated apps

#webpack #parcel #rollup #javascript #web-development

Modesto  Corwin

Modesto Corwin


Webpack, Rollup and Parcel Compared

Let’s build a React app using Webpack, Rollup and Parcel to compare these three bundlers.


#webpack #parcel

Dexter  Goodwin

Dexter Goodwin


Webpack: A Bundler for Javascript and Friends


Webpack is a module bundler. Its main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.


Install with npm:

npm install --save-dev webpack

Install with yarn:

yarn add webpack --dev


Webpack is a bundler for modules. The main purpose is to bundle JavaScript files for usage in a browser, yet it is also capable of transforming, bundling, or packaging just about any resource or asset.


  • Bundles ES Modules, CommonJS, and AMD modules (even combined).
  • Can create a single bundle or multiple chunks that are asynchronously loaded at runtime (to reduce initial loading time).
  • Dependencies are resolved during compilation, reducing the runtime size.
  • Loaders can preprocess files while compiling, e.g. TypeScript to JavaScript, Handlebars strings to compiled functions, images to Base64, etc.
  • Highly modular plugin system to do whatever else your application requires.

Get Started

Check out webpack's quick Get Started guide and the other guides.

Browser Compatibility

Webpack supports all browsers that are ES5-compliant (IE8 and below are not supported). Webpack also needs Promise for import() and require.ensure(). If you want to support older browsers, you will need to load a polyfill before using these expressions.



Webpack has a rich plugin interface. Most of the features within webpack itself use this plugin interface. This makes webpack very flexible.

NameStatusInstall SizeDescription
[mini-css-extract-plugin][mini-css]![mini-css-npm]![mini-css-size]Extracts CSS into separate files. It creates a CSS file per JS file which contains CSS.
[compression-webpack-plugin][compression]![compression-npm]![compression-size]Prepares compressed versions of assets to serve them with Content-Encoding
[html-webpack-plugin][html-plugin]![html-plugin-npm]![html-plugin-size]Simplifies creation of HTML files (index.html) to serve your bundles


Webpack enables the use of loaders to preprocess files. This allows you to bundle any static resource way beyond JavaScript. You can easily write your own loaders using Node.js.

Loaders are activated by using loadername! prefixes in require() statements, or are automatically applied via regex from your webpack configuration.


NameStatusInstall SizeDescription
[val-loader][val]![val-npm]![val-size]Executes code as module and considers exports as JS code


NameStatusInstall SizeDescription
![cson-npm]![cson-size]Loads and transpiles a CSON file


NameStatusInstall SizeDescription
![babel-npm]![babel-size]Loads ES2015+ code and transpiles to ES5 using Babel
![type-npm]![type-size]Loads TypeScript like JavaScript
![coffee-npm]![coffee-size]Loads CoffeeScript like JavaScript


NameStatusInstall SizeDescription
![html-npm]![html-size]Exports HTML as string, requires references to static resources
![pug-npm]![pug-size]Loads Pug templates and returns a function
![md-npm]![md-size]Compiles Markdown to HTML
![posthtml-npm]![posthtml-size]Loads and transforms a HTML file using PostHTML
![hbs-npm]![hbs-size]Compiles Handlebars to HTML


NameStatusInstall SizeDescription
<style>![style-npm]![style-size]Add exports of a module as style to DOM
![css-npm]![css-size]Loads CSS file with resolved imports and returns CSS code
![less-npm]![less-size]Loads and compiles a LESS file
![sass-npm]![sass-size]Loads and compiles a Sass/SCSS file
![stylus-npm]![stylus-size]Loads and compiles a Stylus file
![postcss-npm]![postcss-size]Loads and transforms a CSS/SSS file using PostCSS


NameStatusInstall SizeDescription
![vue-npm]![vue-size]Loads and compiles Vue Components
![polymer-npm]![polymer-size]Process HTML & CSS with preprocessor of choice and require() Web Components like first-class modules
![angular-npm]![angular-size]Loads and compiles Angular 2 Components
![riot-npm]![riot-size]Riot official webpack loader


Webpack uses async I/O and has multiple caching levels. This makes webpack fast and incredibly fast on incremental compilations.

Module Formats

Webpack supports ES2015+, CommonJS and AMD modules out of the box. It performs clever static analysis on the AST of your code. It even has an evaluation engine to evaluate simple expressions. This allows you to support most existing libraries out of the box.

Code Splitting

Webpack allows you to split your codebase into multiple chunks. Chunks are loaded asynchronously at runtime. This reduces the initial loading time.


Webpack can do many optimizations to reduce the output size of your JavaScript by deduplicating frequently used modules, minifying, and giving you full control of what is loaded initially and what is loaded at runtime through code splitting. It can also make your code chunks cache friendly by using hashes.


We want contributing to webpack to be fun, enjoyable, and educational for anyone, and everyone. We have a vibrant ecosystem that spans beyond this single repo. We welcome you to check out any of the repositories in our organization or webpack-contrib organization which houses all of our loaders and plugins.

Contributions go far beyond pull requests and commits. Although we love giving you the opportunity to put your stamp on webpack, we also are thrilled to receive a variety of other contributions including:

  • Documentation updates, enhancements, designs, or bugfixes
  • Spelling or grammar fixes
  • corrections or redesigns
  • Adding unit, or functional tests
  • Triaging GitHub issues -- especially determining whether an issue still persists or is reproducible.
  • Searching #webpack on twitter and helping someone else who needs help
  • Teaching others how to contribute to one of the many webpack's repos!
  • Blogging, speaking about, or creating tutorials about one of webpack's many features.
  • Helping others in our webpack gitter channel.

To get started have a look at our documentation on contributing.

If you are worried or don't know where to start, you can always reach out to Sean Larkin (@TheLarkInn) on Twitter or simply submit an issue and a maintainer can help give you guidance!

We have also started a series on our Medium Publication called The Contributor's Guide to webpack. We welcome you to read it and post any questions or responses if you still need help.

Looking to speak about webpack? We'd love to review your talk abstract/CFP! You can email it to webpack [at] opencollective [dot] com and we can give pointers or tips!!!

Creating your own plugins and loaders

If you create a loader or plugin, we would <3 for you to open source it, and put it on npm. We follow the x-loader, x-webpack-plugin naming convention.


We consider webpack to be a low-level tool used not only individually but also layered beneath other awesome tools. Because of its flexibility, webpack isn't always the easiest entry-level solution, however we do believe it is the most powerful. That said, we're always looking for ways to improve and simplify the tool without compromising functionality. If you have any ideas on ways to accomplish this, we're all ears!

If you're just getting started, take a look at our new docs and concepts page. This has a high level overview that is great for beginners!!

Looking for webpack 1 docs? Please check out the old wiki, but note that this deprecated version is no longer supported.

If you want to discuss something or just need help, here is our Gitter room where there are always individuals looking to help out!

If you are still having difficulty, we would love for you to post a question to StackOverflow with the webpack tag. It is much easier to answer questions that include your webpack.config.js and relevant files! So if you can provide them, we'd be extremely grateful (and more likely to help you find the answer!)

If you are twitter savvy you can tweet #webpack with your question and someone should be able to reach out and help also.

If you have discovered a 🐜 or have a feature suggestion, feel free to create an issue on Github.


Most of the core team members, webpack contributors and contributors in the ecosystem do this open source work in their free time. If you use webpack for a serious task, and you'd like us to invest more time on it, please donate. This project increases your income/productivity too. It makes development and applications faster and it reduces the required bandwidth.

This is how we use the donations:

  • Allow the core team to work on webpack
  • Thank contributors if they invested a large amount of time in contributing
  • Support projects in the ecosystem that are of great value for users
  • Support projects that are voted most (work in progress)
  • Infrastructure cost
  • Fees for money handling

Author: Webpack
Source Code: 
License: MIT License

#webpack #javascript 

Go Programming

Go Programming


Module Bundlers Explained... Webpack, Rollup, Parcel, and Snowpack

What is a Module Bundler? And why do I need one? Learn how tools like Webpack, Rollup, Parcel, and Snowpack can package your code as a production-ready web application.


#webpack #parcel #programming #developer

Carmen  Grimes

Carmen Grimes


An Introduction to the Rollup.js JavaScript Bundler

Snowpack, Webpack and Parcel bundle your JavaScript but are hard to custom configure. Rollup.js is faster and more configurable. Learn how to set it up!

Rollup.js is a next-generation JavaScript module bundler from Rich Harris, the author of Svelte. It compiles multiple source files into a single bundle.

The benefits include:

  • development is easier to manage when using smaller, self-contained source files
  • the source can be linted, prettified, and syntax-checked during bundling
  • tree-shaking removes unused functions
  • transpiling to ES5 for backward compatibility is possible
  • multiple output files can be generated — for example, your library could be provided in ES5, ES6 modules, and Node.js-compatible CommonJS
  • production bundles can be minified and have logging removed

Other bundler options, such as webpack, Snowpack, and Parcel, attempt to magically handle everything: HTML templating, image optimization, CSS processing, JavaScript bundling, and more. This works well when you’re happy with the default settings, but custom configurations can be difficult and processing is slower.

Rollup.js primarily concentrates on JavaScript (although there are plugins for HTML templates and CSS). It has a daunting number of options, but it’s easy to get started and bundling is fast. This tutorial explains how to use typical configurations within your own projects.

#javascript #rollup #snowpack #webpack #parcel