The webpack-dev-server is a little Node.js Express server, which uses the webpack-dev-middleware to serve a webpack bundle. It also has a little runtime which is connected to the server via Sock.js.
The server emits information about the compilation state to the client, which reacts to those events. You can choose between different modes, depending on your needs.
Let’s say you have the following config file (webpack.config.js):
var path = require("path");
module.exports = {
entry: {
app: ["./app/main.js"]
},
output: {
path: path.resolve(__dirname, "build"),
publicPath: "/assets/",
filename: "bundle.js"
}
};
You have an app folder with your initial entry point that webpack will bundle into a bundle.js file in the build folder.
NOTE: The webpack dev server is a separate NPM package. You can install it with: npm install webpack-dev-server.
The webpack-dev-server will serve the files in the current directory, unless you configure a specific content base.
$ webpack-dev-server --content-base build/
Using this configuration, webpack-dev-server will serve the static files in your build folder. It’ll watch your source files, and recompile the bundle whenever they are changed.
This modified bundle is served from memory at the relative path specified in publicPath (see API). It will not be written to your configured output directory. Where a bundle already exists at the same URL path, the bundle in memory takes precedence (by default).
Using the configuration above, the bundle is available at localhost:8080/assets/bundle.js.
To load your bundled files, you will need to create an index.html file in the build folder from which static files are served (--content-base option). Here’s an example:
<!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <title>Document</title> </head> <body> <script src="assets/bundle.js"></script> </body> </html>
By default, go to localhost:8080/ to launch your app. In this example’s configuration (with publicPath), go to localhost:8080/assets/.
The webpack-dev-server supports multiple modes to automatically refresh the page:
iframe and reloaded on change)Each mode also supports Hot Module Replacement. In Hot Module replacement, the bundle is notified that a change happened (rather than a full page reload). A Hot Module Replacement runtime could then load the updated modules and inject them into a running app.
To use the iframe mode no additional configuration is needed. Just navigate the browser to http://«host»:«port»/webpack-dev-server/«path».
With the above configuration: http://localhost:8080/webpack-dev-server/index.html.
To use the inline mode, either
--inline on the command line.devServer: { inline: true } in your webpack.config.js
This adds the webpack-dev-server client entry point to the webpack configuration. There is no change in the URL required. Just navigate to http://«host»:«port»/«path».
With the above configuration: http://localhost:8080/index.html.
There is no inline: true flag in the webpack-dev-server configuration, because the webpack-dev-server module has no access to the webpack configuration. Instead, the user must add the webpack-dev-server client entry point to the webpack configuration.
To do this, simply add the following to all entry points: webpack-dev-server/client?http://«path»:«port»/
With the above configuration:
var config = require("./webpack.config.js");
config.entry.app.unshift("webpack-dev-server/client?http://localhost:8080/");
var compiler = webpack(config);
var server = new WebpackDevServer(compiler, {...});
server.listen(8080);
There is also the option to add a reference to the webpack-dev-server client script to the HTML page:
<script src="http://localhost:8080/webpack-dev-server.js"></script>
To enable Hot Module Replacement with the webpack-dev-server specify --hot on the command line. This adds the HotModuleReplacementPlugin to the webpack configuration.
The easiest way to use Hot Module Replacement with the webpack-dev-server is to use the inline mode.
Nothing more is needed. --inline --hot does all the relevant work automatically. The CLI of the webpack-dev-server automatically adds the special webpack/hot/dev-server entry point to your configuration.
Just navigate to http://«host»:«port»/«path» and let the magic happen.
You should see the following messages in the browser log:
[HMR] Waiting for update signal from WDS... [WDS] Hot Module Replacement enabled.
Messages prefixed with [HMR] originate from the webpack/hot/dev-server module. Messages prefixed with [WDS] originate from the webpack-dev-server client.
It’s important to specify a correct output.publicPath otherwise the hot update chunks cannot be loaded.
Similar to the inline mode the user must make changes to the webpack configuration.
Three changes are needed:
webpack/hot/dev-server.new webpack.HotModuleReplacementPlugin() to the webpack configuration.hot: true to the webpack-dev-server configuration to enable HMR on the server.With the above configuration:
var config = require("./webpack.config.js");
config.entry.app.unshift("webpack-dev-server/client?http://localhost:8080/", "webpack/hot/dev-server");
var compiler = webpack(config);
var server = new webpackDevServer(compiler, {
hot: true
...
});
server.listen(8080);
Note that many editors support “safe write” feature and have it enabled by default, which makes dev server unable to watch files correctly. “Safe write” means changes are not written directly to original file but to temporary one instead, which is renamed and replaces original file when save operation is completed successfully. This behaviour causes file watcher to lose the track because the original file is removed. In order to prevent this issue, you have to disable “safe write” feature in your editor.
:set backupcopy=yes (see documentation)safe write (may differ in various IntelliJ IDEs, but you can still use the search feature)The Webpack dev server makes use of http-proxy-middleware to optionally proxy requests to a separate, possibly external, backend server. A sample configuration is below.
proxy: {
'/api': {
target: 'https://other-server.example.com',
secure: false
}
}
// In webpack.config.js
{
devServer: {
proxy: {
'/api': {
target: 'https://other-server.example.com',
secure: false
}
}
}
}
// Multiple entry
proxy: [
{
context: ['/api-v1/**', '/api-v2/**'],
target: 'https://other-server.example.com',
secure: false
}
]
See the http-proxy-middleware Options documentation for available configuration.
Proxying some URLs can be useful for a variety of configurations. One example is to serve JavaScript files and other static assets from the local development server but still send API requests to an external backend development server. Another example is splitting requests between two separate backend servers such as an authentication backend and a application backend.
(Added in v1.13.0) The proxy can be optionally bypassed based on the return from a function. The function can inspect the HTTP request, response, and any given proxy options. It must return either false or a URL path that will be served instead of continuing to proxy the request.
For example, the configuration below will not proxy HTTP requests that originate from a browser. This is similar to the historyApiFallback option: browser requests will receive the HTML file as normal but API requests will be proxied to the backend server.
proxy: {
'/some/path': {
target: 'https://other-server.example.com',
secure: false,
bypass: function(req, res, proxyOptions) {
if (req.headers.accept.indexOf('html') !== -1) {
console.log('Skipping proxy for browser request.');
return '/index.html';
}
}
}
(Added in v1.15.0) The request to the proxy can be optionally rewritten by providing a function. The function can inspect and change the HTTP request.
For example, the configuration below will rewrite the HTTP requests to remove the part /api at the beginning of the URL.
proxy: {
'/api': {
target: 'https://other-server.example.com',
pathRewrite: {'^/api' : ''}
}
}
Note that pathRewrite is a feature from http-proxy-middleware, so check out their docs for more configuration.
It seems that http-proxy-middleware pre-resolves the local hostnames into localhost, you will need the following config to fix the proxy request:
var server = new webpackDevServer(compiler, {
quiet: false,
stats: { colors: true },
proxy: {
"/api": {
"target": {
"host": "action-js.dev",
"protocol": 'http:',
"port": 80
},
ignorePath: true,
changeOrigin: true,
secure: false
}
}
});
server.listen(8080);
$ webpack-dev-server <entry>
All webpack CLI options are valid for the webpack-dev-server CLI too, but there is no <output> default argument. For the webpack-dev-server CLI a webpack.config.js (or the file passed by the --config option) is accepted as well.
There are some additional options:
--content-base <file/directory/url/port>: base path for the content.--quiet: don’t output anything to the console.--no-info: suppress boring information.--colors: add some colors to the output.--no-colors: don’t use colors in the output.--compress: use gzip compression.--host <hostname/ip>: hostname or IP. 0.0.0.0 binds to all hosts.--port <number>: port.--inline: embed the webpack-dev-server runtime into the bundle.--hot: adds the HotModuleReplacementPlugin and switch the server to hot mode. Note: make sure you don’t add HotModuleReplacementPlugin twice.--hot --inline also adds the webpack/hot/dev-server entry.--public: overrides the host and port used in --inline mode for the client (useful for a VM or Docker).--lazy: no watching, compiles on request (cannot be combined with --hot).--https: serves webpack-dev-server over HTTPS Protocol. Includes a self-signed certificate that is used when serving the requests.--cert, --cacert, --key: Paths the certificate files.--open: opens the url in default browser (for webpack-dev-server versions > 2.0).--history-api-fallback: enables support for history API fallback.--client-log-level: controls the console log messages shown in the browser. Use error, warning, info or none.When using the CLI it’s possible to have the webpack-dev-server options in the configuration file under the key devServer. Options passed via CLI arguments override options in configuration file. For options under devServer see next section.
Example
module.exports = {
// ...
devServer: {
hot: true
}
}
var WebpackDevServer = require("webpack-dev-server");
var webpack = require("webpack");
var compiler = webpack({
// configuration
});
var server = new WebpackDevServer(compiler, {
// webpack-dev-server options
contentBase: "/path/to/directory",
// Can also be an array, or: contentBase: "http://localhost/",
hot: true,
// Enable special support for Hot Module Replacement
// Page is no longer updated, but a "webpackHotUpdate" message is sent to the content
// Use "webpack/hot/dev-server" as additional module in your entry point
// Note: this does _not_ add the `HotModuleReplacementPlugin` like the CLI option does.
historyApiFallback: false,
// Set this as true if you want to access dev server from arbitrary url.
// This is handy if you are using a html5 router.
compress: true,
// Set this if you want to enable gzip compression for assets
proxy: {
"**": "http://localhost:9090"
},
// Set this if you want webpack-dev-server to delegate a single path to an arbitrary server.
// Use "**" to proxy all paths to the specified server.
// This is useful if you want to get rid of 'http://localhost:8080/' in script[src],
// and has many other use cases (see https://github.com/webpack/webpack-dev-server/pull/127 ).
setup: function(app) {
// Here you can access the Express app object and add your own custom middleware to it.
// For example, to define custom handlers for some paths:
// app.get('/some/path', function(req, res) {
// res.json({ custom: 'response' });
// });
},
// pass [static options](http://expressjs.com/en/4x/api.html#express.static) to inner express server
staticOptions: {
},
clientLogLevel: "info",
// Control the console log messages shown in the browser when using inline mode. Can be `error`, `warning`, `info` or `none`.
// webpack-dev-middleware options
quiet: false,
noInfo: false,
lazy: true,
filename: "bundle.js",
watchOptions: {
aggregateTimeout: 300,
poll: 1000
},
// It's a required option.
publicPath: "/assets/",
headers: { "X-Custom-Header": "yes" },
stats: { colors: true }
});
server.listen(8080, "localhost", function() {});
// server.close();
See webpack-dev-middleware for documentation on middleware options.
Notice that webpack configuration is not passed to WebpackDevServer API, thus devServer option in webpack configuration is not used in this case. Also, there is no inline mode for WebpackDevServer API. <script src="http://localhost:8080/webpack-dev-server.js"></script> should be inserted to HTML page manually.
historyApiFallback optionIf you are using the HTML5 history API you probably need to serve your index.html in place of 404 responses, which can be done by setting historyApiFallback: true. However, if you have modified output.publicPath in your Webpack configuration, you need to specify the URL to redirect to. This is done using the historyApiFallback.index option:
// output.publicPath: '/foo-app/'
historyApiFallback: {
index: '/foo-app/'
}
Using rewrites, it is also possible to use this feature to serve static pages:
historyApiFallback: {
rewrites: [
// shows views/landing.html as the landing page
{ from: /^\/$/, to: '/views/landing.html' },
// shows views/subpage.html for all routes starting with /subpage
{ from: /^\/subpage/, to: '/views/subpage.html' },
// shows views/404.html on all other pages
{ from: /./, to: '/views/404.html' },
],
},
You may want to run a backend server or a mock of it in development. You should not use the webpack-dev-server as a backend. Its only purpose is to serve static (webpacked) assets.
You can run two servers side-by-side: The webpack-dev-server and your backend server.
In this case you need to teach the webpack-generated assets to make requests to the webpack-dev-server even when running on a HTML-page sent by the backend server. On the other side you need to teach your backend server to generate HTML pages that include script tags that point to assets on the webpack-dev-server. In addition to that you need a connection between the webpack-dev-server and the webpack-dev-server runtime to trigger reloads on recompilation.
To teach webpack to make requests (for chunk loading or HMR) to the webpack-dev-server you need to provide a full URL in the output.publicPath option.
To make a connection between webpack-dev-server and its runtime best, use the inline mode with --inline. The webpack-dev-server CLI automatically includes an entry point which establishes a WebSocket connection. (You can also use the iframe mode if you point --content-base of the webpack-dev-server to your backend server. If you need a websocket connection to your backend server, you’ll have to use iframe mode.
When you use the inline mode just open the backend server URL in your web browsers. (If you use the iframe mode open the /webpack-dev-server/ prefixed URL of the webpack-dev-server.)
Summary and example:
8080.9090.<script src="http://localhost:8080/assets/bundle.js">.output.publicPath = "http://localhost:8080/assets/".--output-public-path /assets/.--inline.http://localhost:9090.contentBase = "http://localhost:9090/" (--content-base).http://localhost:8080/webpack-dev-server/.Or use the proxy option…
© 2012–2016 Tobias Koppers
Licensed under the MIT License.
https://webpack.github.io/docs/webpack-dev-server.html