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 :sparkles:
You rock!
:palm_tree:
The new version differs by 227 commits (ahead by 227, behind by 21).
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.
Hello lovely humans,
webpack-dev-server just published its new version 2.2.1.
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 :sparkles:
You rock!
:palm_tree:
The new version differs by 227 commits (ahead by 227, behind by 21).
aa989972.2.1686dec4Fix inline example not working after webpack 2.2.0c82c1ebOnly run Travis on themasterbranch [skip ci]54b4b02update examples to reflect web pack 2.2.0 (#759)3bc7f77webpack.github.io -> webpack.js.orgcb98dd9Change link in readme to webpack.js.org31fb4fdAdded example "webworker" (#755)7e18f6a2.2.0e9dd0edUpgrade webpack dependencycae704fUpdate README to new standardd560695Fix broken test after webpack update84a98adupdate webpack dev dependencya947336Refactor to ES6fb74672Bring eslint config in line with webpack/webpack2f9ac82Make Travis run Node.js v4 and v6There are 227 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.