Update webpack-dev-server to version 2.4.3 🚀

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447

[greenkeeperio-bot]

Hello lovely humans,

webpack-dev-server just published its new version 2.4.3.

State	Update 🚀
Dependency	webpack-dev-server
New version	2.4.3
Type	devDependency

This version is not covered by your current version range.

Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

I recommend you look into these changes and try to get onto the latest version of webpack-dev-server.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.

Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?

There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.

Good luck with your project ✨

You rock!

🌴

---

GitHub Release

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

---

The new version differs by 259 commits (ahead by 259, behind by 34).

• ca932842.4.3
• f3a4ac6Merge branch 'security/host-check'
• 8db5fd5Require a secure webpack-dev-middleware version
• 2957853enable Host header check for all requests and sockets
• 60e47272.4.2
• 32adae3Added beforeunload check to index.js (#544) (#841)
• d69559aHandle external upgrade for all websocket proxies (#843)
• 35a44d1Remove Node.js v7 warning
• d2f579cSupport for array of contentBase (#832)
• aabeeaaRemove unnecessary logging of closing the dev-server
• 1dc9461Fix to share proxy option between proxy settings when the proxy option is a same object (#836)
• 42cd23cExplicitely but gracefully handle SIGINT and SIGTERM signals. (#787)
• 85de417Use arrow function if it possible and get rid of .bind in server part (#835)
• 234294aAdd unit tests for proxy options (#834)
• 8d4b826add codecov

There are 250 commits in total. See the full diff.

---

✨ Try the all new Greenkeeper GitHub Integration ✨
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever. Screencast Try it today. Free for private repositories during beta.

[coveralls]

Coverage increased (+0.3%) to 89.298% when pulling ef3986c on greenkeeper-webpack-dev-server-2.4.3 into 020295b on master.

[instantlinux]

replaced by #447