You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 8, 2019. It is now read-only.
Tobias Koppers edited this page Feb 4, 2014
·
19 revisions
webpack is a module bundler.
This means webpack takes modules with dependencies and emit static assets representing that modules.
Why another module bundler?
Existing module bundlers are not well suited for big projects (big single page application). The most pressing reason for developing another module bundler was Code Splitting. Another one was that other static assets should fit seamless in the modularization.
I tried to extend existing module bundlers, but it wasn't possible to archive all goals.
Goals
Split the dependency tree into chunks, that are loaded on demand
Every static asset should be able to be a module
Keep initial loading time low
Ability to integrate 3rd-party libraries as modules
Ability to customize nearly every part of the module bundler