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

rollup

1.8K
163
+ 1
17
Webpack

40.6K
27.4K
+ 1
752
Add tool

Webpack vs rollup: What are the differences?

Introduction

In this Markdown code, we will discuss the key differences between Webpack and Rollup. Both are popular module bundlers used in web development. Understanding their differences can help developers choose the most suitable tool for their projects.

  1. Tree-Shaking: Webpack and Rollup differ in how they handle tree-shaking, which is the process of eliminating dead code from the final bundle. Webpack uses static analysis to determine which modules are used and excludes the ones that are not, resulting in a larger bundle size. On the other hand, Rollup performs more advanced analysis and can achieve better tree-shaking, resulting in smaller bundle sizes.

  2. Code Splitting: When it comes to code splitting, Webpack and Rollup have different approaches. Webpack supports both dynamic and static code splitting, allowing developers to split their code into separate chunks that can be loaded on demand. Rollup, on the other hand, focuses more on static code splitting, which means that splitting happens at build time and not dynamically at runtime.

  3. Configuration: The configuration of Webpack and Rollup also differs. Webpack has a more complex configuration system with multiple configuration files and various plugins. This flexibility allows developers to customize the bundling process to a greater extent. On the other hand, Rollup has a simpler configuration system with a single configuration file, making it easier to set up and get started.

  4. Development vs Production: Webpack and Rollup also differ in their primary use cases. Webpack is often preferred for larger projects or projects that require more development-oriented features like hot module replacement and code splitting. Rollup, on the other hand, is commonly used for production builds where the focus is on producing efficient and optimized output.

  5. Bundle Formats: Both Webpack and Rollup support different bundle formats. Webpack primarily generates bundles in the CommonJS or AMD format, which are suitable for development environments. Rollup, on the other hand, excels at generating bundles in the ES module format, making it compatible with modern JavaScript development workflows.

  6. Performance: When it comes to performance, Webpack and Rollup have different trade-offs. Webpack is known for its efficiency in handling larger codebases and complex setups. It offers various optimizations and features that cater to the needs of larger projects but can come at the cost of longer build times. Rollup, on the other hand, is designed to be faster and more lightweight, making it a suitable choice for smaller projects or projects where build speed is crucial.

In summary, Webpack and Rollup have key differences in tree-shaking, code splitting, configuration, primary use cases, bundle formats, and performance. Understanding these differences can help developers choose the appropriate tool for their specific project requirements.

Decisions about rollup and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 291.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
Manage your open source components, licenses, and vulnerabilities
Learn More
Pros of rollup
Pros of Webpack
  • 4
    Makes it easy to publish packages
  • 3
    Easier configuration
  • 2
    Better tree shaking
  • 2
    Provides smaller bundle size
  • 1
    Integrates seamlessly with SystemJS
  • 1
    Produces very clean code
  • 1
    Very reliable
  • 1
    Very robust Plugin-API (years old Plugins still work)
  • 1
    Very flexible
  • 1
    Was built with ESM-Modules in mind
  • 309
    Most powerful bundler
  • 182
    Built-in dev server with livereload
  • 142
    Can handle all types of assets
  • 87
    Easy configuration
  • 22
    Laravel-mix
  • 4
    Overengineered, Underdeveloped
  • 2
    Makes it easy to bundle static assets
  • 2
    Webpack-Encore
  • 1
    Redundant
  • 1
    Better support in Browser Dev-Tools

Sign up to add or upvote prosMake informed product decisions

Cons of rollup
Cons of Webpack
  • 1
    No clear path for static assets
  • 1
    No Loader like Webpack (need to use sjs or ESM imports)
  • 1
    Almost everything needs to be a Plugin
  • 1
    Manual Chunking is a bit buggy
  • 15
    Hard to configure
  • 5
    No clear direction
  • 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

Sign up to add or upvote consMake informed product decisions

- No public GitHub repository available -

What is 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.

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 rollup?
What companies use Webpack?
Manage your open source components, licenses, and vulnerabilities
Learn More

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

What tools integrate with rollup?
What tools integrate with Webpack?

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

What are some alternatives to rollup and Webpack?
Angular CLI
A command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications. You can use the tool directly in a command shell, or indirectly through an interactive UI such as Angular Console.
Parcel
Parcel is a web application bundler, differentiated by its developer experience. It offers blazing fast performance utilizing multicore processing, and requires zero configuration.
Babel
Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support.
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.
Browserify
Browserify lets you require('modules') in the browser by bundling up all of your dependencies.
See all alternatives