Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Webpack vs Angular, the Slant community recommends Webpack for most people. In the question“What are the best frontend JavaScript module bundlers?” Webpack is ranked 1st while Angular is ranked 9th. 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.
Question Ranking
Pros
Pro Rich and flexible plugin infrastructure
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.
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.
Pro Mix ES6 AMD and CommonJS
Webpack supports using all three module types, even in the same file.
Pro Limit plugin integration issues
Pro Great tooling and language support
Very good CLI and webpack, bundling, testing, deployment support. Deep TypeScript integration and support.
Cons
Con Config file may be hard to understand
Due to a somewhat hard to grasp syntax, configuring Webpack may take some time.
Con Can not load files discovered during runtime
Con Slightly over-engineered
Very enterprisey - made for huge architectures and with tons of declarative, non-intuitive annotations it makes it overkill for very small projects.
Con Native i18n support over-engineered
Not developer-friendly. Switching languages need reloading the whole page. There are third party solutions that work better.
