Here’s the Deal

Webpack vs module-concat

107 17

1 0

When comparing Webpack vs module-concat, the Slant community recommends Webpack for most people. In the question“What are the best frontend JavaScript module bundlers?” Webpack is ranked 1st while module-concat is ranked 15th. The most important reason people chose Webpack is:

Plugins and loaders are easy to write and allow you to control each step of the build, from loading and compiling CoffeeScript, LESS and JADE files to smart post processing and asset manifest building.

Ranked in these QuestionsQuestion Ranking

Common Questions

What are the best frontend JavaScript module bundlers?

Pros

Pro
Rich and flexible plugin infrastructure

Pro
Tap into npm's huge module ecosystem

Using Webpack opens you up to npm, that has over 80k modules of which a great amount work both client-side and server-side. And the list is growing rapidly.

Pro
Can create a single bundle or multiple chunks loaded on demand, to reduce initial loading time

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

Pro
Supports source maps for easier debugging

Source maps allow for easier debugging, because they allow you to find the problems within the origin files instead of the output file.

Pro
ES6 module support

Webpack supports ES6 modules and their import and export methods without having to compile them to CommonJS require

Pro
Share the same modules client-side and server-side

Because Webpack allows you to use the same require() function as node.js, you can easily share modules between the client-side and server-side.

Pro
Bundles CommonJs and AMD modules (even combined)

Webpack supports AMD and CommonJS module styles. 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.