Need advice about which tool to choose?Ask the StackShare community!
Closure Compiler vs Webpack: What are the differences?
Introduction
This Markdown code provides a comparison between Closure Compiler and Webpack, highlighting their key differences.
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.
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.
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.
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.
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.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.
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 thannpm 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.
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.
Pros of Closure Compiler
- The best performing output1
- Small output size1
- Dead code elimination1
- ES6 support1
- Bundle support for CommonJS, ES6, .1
- Ease0
Pros of Webpack
- Most powerful bundler309
- Built-in dev server with livereload182
- Can handle all types of assets142
- Easy configuration87
- Laravel-mix22
- Overengineered, Underdeveloped4
- Makes it easy to bundle static assets2
- Webpack-Encore2
- Redundant1
- Better support in Browser Dev-Tools1
Sign up to add or upvote prosMake informed product decisions
Cons of Closure Compiler
Cons of Webpack
- Hard to configure15
- No clear direction5
- Spaghetti-Code out of the box2
- SystemJS integration is quite lackluster2
- Loader architecture is quite a mess (unreliable/buggy)2
- Fire and Forget mentality of Core-Developers2