It's a simple wrapper middleware for webpack. It serves the files emitted from webpack over a connect server. This should be used for development only.
It has a few advantages over bundling it as files:
npm install webpack-dev-middleware --save-dev
var webpackMiddleware = ;app;
This part shows how you might interact with the middleware during runtime:
close(callback) - stop watching for file changes
var webpackDevMiddlewareInstance = ;app;// After 10 seconds stop watching for file changes:;
invalidate() - recompile the bundle - e.g. after you changed the configuration
var compiler = ;var webpackDevMiddlewareInstance = ;app;;
waitUntilValid(callback) - executes the
callback if the bundle is valid or after it is valid again:
var webpackDevMiddlewareInstance = ;app;webpackDevMiddlewareInstance;
Note: this feature is experimental and may be removed or changed completely in the future.
In order to develop a server-side rendering application, we need access to the
stats, which is generated with the latest build.
In the server-side rendering mode, webpack-dev-middleware would sets the
res.locals.webpackStats before invoking the next middleware, where we can render pages and response to clients.
Notice that requests for bundle files would still be responded by webpack-dev-middleware and all requests will be pending until the building process is finished in the server-side rendering mode.
Don't hesitate to create a pull request. Every contribution is appreciated. In development you can start the tests by calling