v2.4.1

• After fixing a warning/error, the overlay was not always cleared correctly (3cb79bd).

v2.4.0

• contentBase: false in combination with the historyApiFallback option threw an error (#791).
• Separate logic of adding entry points to the webpack config; this allows alternative implementations like the webpack grunt plugin to use this instead of copying the code (#782).
• Update SockJS dependency to fix issue with FireFox constantly refreshing the page (#762).
• Show clear error message when --open fails to open the browser (#780).
• Allow overlay option to also show compiler warnings (off by default) (#790):

overlay: {
  errors: true,
  warnings: true
}

v2.3.0

• Add new fancy error overlay in-browser, which shows up when there are compilation errors. Disabled by default, add overlay: true to enable (#764)!
• If you use --open and options.public, the browser will now open the same URL as you have defined in public (#749).
• options.port now allows strings to be passed in, previously only integers were accepted (#766).

v1.16.3

Probably the last release in the v1.x range:

• Backport support for webpack config as a Promise.

v2.2.0

First webpack-dev-server 2 release

Following the webpack 2 release.
It's equal to the last RC.

If you're curious about the highlights, read this fancy Medium post.

v2.2.0-rc.0

• Allow latest webpack 2.2.0-rc.0 as peer dependency (#714).

v2.1.0-beta.12

• beta.11 prevented the page from reloading when there was an error or a warning. Now it will only prevent a reload when there are errors, since you can ignore warnings (#697).
• beta.11 introduced configuration validation. There was a small error that prevented clientLogLevel: "none" from working (#693).
• Fix startup information not using colors in some cases (8a4b070).

v2.1.0-beta.11

• Breaking change: all options passed to the server get validated now, just like the webpack options already are. In most cases this shouldn't break anything, but it is possible we missed some valid usages (#654).
• webpack 2.1.0-beta.26 or higher is required.
• If no port is specified, the CLI will now find the first available port that is not in use instead of crashing when port 8080 is in use (#685).
• When the webpack compiler threw an error or warning, the page would be reloaded. Now, it doesn't reload the page (#209).
• The startup information that denotes the URL, path etc. is more fancy now and uses colors (#681).
• Fix --version flag not working in CLI (#679).
• Fix --open flag opening the wrong URL when using lazy mode (7cb0490).
• Compilation errors were duplicated in the DevTools (webpack/webpack#3008).
• Expose events to the page, so e.g. plugins can show a custom error modal in the browser (#481).

v2.1.0-beta.10

• Breaking change: only support Node.js 0.12 and higher.
• Update SSL certificate in https mode to fix issues with Windows (#648).
• Add option to listen on unix socket instead of a port with the --socket flag (#661).
• Add deprecation warnings for using contentBase with a URL or port, since the proxy option does about the same and is more powerful (61b46ba).
• Fix more issues with IPv6 (#676).

v2.1.0-beta.9

• Add support for watching files provided by the contentBase option. Enable with watchContentBase: true or --watch-content-base in the CLI (#649).
• Support IPv6 addresses as host option (#644).
• Fix historyApiFallback taking preference of contentBase files instead of the in-memory files; this caused issues with html-webpack-plugin (#640).
• Fix edge case where rapidly refreshing the page caused the server to crash (#637).