Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jade, coffee, css, less, ... and your custom stuff.
- bundles CommonJs and AMD modules. (even combined)
- can create a single bundle or multiple chunks loaded on demand, to reduce initial loading time.
- dependencies are resolved during compilation reducing the runtime size
Check the documentation if you want to know more...
npm install webpack --save-dev
npm install webpack -g
Take a look at the
webpack has a rich plugin interface. Most of the features within webpack itself use this plugin interface. This makes webpack very flexible.
webpack uses async I/O and has multiple caching levels. This makes webpack fast and incredibly fast on incremental compilations.
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.
webpack allows you to split your codebase into multiple chunks. Chunks are loaded on demand. This reduces the initial loading time.
webpack can do many optimizations to reduce the output size. It also can make your chunks cache friendly by using hashes.
// webpack is a module bundler// This means webpack takes modules with dependencies// and emits static assets representing those modules.// dependencies can be written in CommonJsvar commonjs = require"./commonjs";// or in AMDdefine"amd-module" "../file"// while previous constructs are sync// this is asyncrequire"big-module/big/file"// for async dependencies webpack splits// your application into multiple "chunks".// This part of your application is// loaded on demand (Code Splitting)var stuff = require"../my/stuff";// "../my/stuff" is also loaded on demand// because it's in the callback function// of the AMD require;;require"coffee!./cup.coffee";// "Loaders" can be used to preprocess files.// They can be prefixed in the require call// or configured in the configuration.require"./cup";// This does the same when you add ".coffee" to the extensions// and configure the "coffee" loader for /\.coffee$/return require"./templates/" + name + ".jade";// many expressions are supported in require calls// a clever parser extracts information and concludes// that everything in "./templates" that matches// /\.jade$/ should be included in the bundle, as it// can be required.// ... and you can combine everythingrequire"bundle?lazy!./templates/" + name + ".jade"templateBundlecallback;;
You can run the browser tests:
cd test/browsertestsnode build
tests.html in browser.
You are welcome to contribute by opening an issue or a pull request. It would be nice if you open sourced your own loaders or webmodules. :)
You are also welcome to correct any spelling mistakes or any language issues, because my english is not perfect...
If you want to discuss something or just need help, here is a gitter.im room.
Copyright (c) 2012-2014 Tobias Koppers
This is a freetime project. My time investment fluctuates randomly. If you use webpack for a serious task you may want me to invest more time. Or if you make some good revenue you can give some money back. Keep in mind that this project may increase your income. It makes development and applications faster and reduces the required bandwidth.
I'm very thankful for every dollar. If you leave your username or email I may show my thanks by giving you extra support.