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 karma-webpack.
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.
When updating to "webpack": "2.2.0-rc.4" & "karma-webpack": "2.0.0" you have to pull the entry property if it's set to an empty object so it defaults to a function within karma-webpack
Hello lovely humans,
karma-webpack just published its new version 2.0.0.
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 karma-webpack. 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:
GitHub Release
Bug Fixes
BREAKING CHANGES
When updating to
"webpack": "2.2.0-rc.4"&"karma-webpack": "2.0.0"you have to pull theentryproperty if it's set to an empty object so it defaults to a function within karma-webpackThe new version differs by 57 commits .
1f13a86chore(release): karma-webpack v2.0.09fd5fdfchore(package): update webpack peerDependencies70dbb24style(lint): lint fixes (#195)2723439fix(config): webpack rc4 schema enforcment (fixes #193)db1a2681.8.1e5abb54Merge pull request #187 from webpack/d3viant0ne-UpdatePeerDeps5716c6dchore(package.json): Allow for webpack 2 rcdd98a6echore(package): allow Webpack 2.2.0 rc as peerDepbe40420chore(build): Remove logout when npm publish is donea5120bechore(release): karma-webpack 1.8.05a4ec1achore(build): remove webpack dev deps and fix generate changelog scriptda82677Merge pull request #163 from webpack/d3viant0ne-BabelBuild9649e99chore(build): Adds travis matrixae35f64chore(build): Use babel rc8be5e12chore(build): Reworks babel buildThere are 57 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade