webpack for browserify users

Usage Like browserify, webpack analyzes all the node-style require() calls in your app and builds a bundle that you can serve

2016-11-24 04:40:20
Testing

There are two ways to test web applications: In-browsers: You get a more realistic test, but you need some more complex infrastructure

2016-11-24 04:40:19
Build performance

Incremental builds Make sure you don?t do a full rebuild. webpack has a great caching layer that allows to keep already compiled modules in

2016-11-24 04:40:12
How to write a loader

A loader is a node module exporting a function. This function is called

2016-11-24 04:40:15
Stylesheets

embedded stylesheets Through using the style-loader and the css-loader it?s possible to embed stylesheets into a

2016-11-24 04:40:19
Code Splitting

For big web apps it?s not efficient to put all code into a single file, especially if some blocks of code are only required under some circumstances. Webpack has a feature

2016-11-24 04:40:12
Library and externals

You developed a library and want to distribute it in compiled/bundled versions (in addition to the modularized version). You want to allow the user to use it in a &l

2016-11-24 04:40:16
AMD

AMD (Asynchronous Module Definition) was the response to those who thought the CommonJS Module system was not ready for the browser because its nature was synchronous.

2016-11-24 04:40:10
Multiple entry points

Prerequirement: Code Splitting If you need multiple bundles

2016-11-24 04:40:18
How to write a plugin

Plugins expose the full potential of the Webpack engine to third-party developers. Using staged build callbacks, developers can introduce their own behaviors into the Webpack

2016-11-24 04:40:15