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

Closure Compiler

203
62
+ 1
5
Webpack

40.5K
27.3K
+ 1
752
Add tool

Closure Compiler vs Webpack: What are the differences?

Introduction

This Markdown code provides a comparison between Closure Compiler and Webpack, highlighting their key differences.

  1. File Types and Languages Supported: Closure Compiler is primarily designed for optimizing JavaScript, while Webpack is a module bundler that supports multiple file types, including JavaScript, CSS, and HTML. Closure Compiler also supports TypeScript, whereas Webpack requires additional configuration to work with TypeScript files.

  2. Optimization Approach: Closure Compiler focuses on advanced techniques like dead code elimination, inlining, and aggressive variable renaming to produce highly optimized code. On the other hand, Webpack's optimization is mainly focused on bundling and code splitting, allowing developers to create efficient bundles for web applications.

  3. Build Process and Configuration: Closure Compiler requires the use of a command-line interface or build tools for optimization and minification. It requires explicit configuration to define the desired optimization level and fine-tune the output. In contrast, Webpack simplifies the build process through a configuration file, where developers can define various loaders and plugins to handle different file types and perform optimization.

  4. Bundle Size and Code Splitting: Closure Compiler analyzes the entire codebase and produces a single optimized output file, resulting in a relatively smaller bundle size. Webpack, on the other hand, enables code splitting, allowing developers to split large bundles into smaller chunks, resulting in more efficient loading and caching of code.

  5. Module System Support: Closure Compiler provides a built-in module system that allows developers to write modular code by using the goog.module syntax. It also supports compatibility with CommonJS and AMD modules. In contrast, Webpack supports a wide range of module systems, including CommonJS, AMD, ES2015 modules, and more, making it highly versatile.

  6. Ecosystem and Community Support: Closure Compiler is a part of the Google Closure Tools suite and has a dedicated user community. It offers various libraries and tools for JavaScript development. Webpack, on the other hand, has a vibrant ecosystem with a large number of plugins and loaders contributed by the community, providing extensive features and integrations for web development.

In summary, Closure Compiler is a specialized tool focused on optimizing JavaScript code with advanced techniques, while Webpack is a versatile module bundler offering optimization, code splitting, and extensive community support for a wide range of file types and module systems.

Decisions about Closure Compiler and Webpack
Aleksandr Filatov
Contract Software Engineer - Microsoft · | 4 upvotes · 289.5K 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 Closure Compiler
Pros of Webpack
  • 1
    The best performing output
  • 1
    Small output size
  • 1
    Dead code elimination
  • 1
    ES6 support
  • 1
    Bundle support for CommonJS, ES6, .
  • 0
    Ease
  • 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 Closure Compiler
Cons of Webpack
    Be the first to leave a con
    • 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

    What is Closure Compiler?

    The Closure Compiler is a tool for making JavaScript download and run faster. It is a true compiler for JavaScript. Instead of compiling from a source language to machine code, it compiles from JavaScript to better JavaScript. It parses your JavaScript, analyzes it, removes dead code and rewrites and minimizes what's left. It also checks syntax, variable references, and types, and warns about common JavaScript pitfalls.

    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!

    Jobs that mention Closure Compiler and Webpack as a desired skillset
    What companies use Closure Compiler?
    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 Closure Compiler?
    What tools integrate with Webpack?

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

    What are some alternatives to Closure Compiler and Webpack?
    Babel
    Babel will turn your ES6+ code into ES5 friendly code, so you can start using it right now without waiting for browser support.
    UglifyJS
    This package implements a general-purpose JavaScript parser/compressor/beautifier toolkit. It is developed on NodeJS, but it should work on any JavaScript platform supporting the CommonJS module system (and if your platform of choice doesn’t support CommonJS, you can easily implement it, or discard the exports.* lines from UglifyJS sources).
    TypeScript
    TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript.
    JavaScript
    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
    Git
    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
    See all alternatives