The version 1.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of mocha-webpack.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv1.0.0
use memory-fs instead of writing bundle to disk
include source-map-support by default
replaced the "glob-like" file resolution with real glob
support multiple entry files/patterns/directories
respect defined file extensions in resolve.extensions for directory entries
support custom reporters with relative file paths
pretty status logging & pretty webpack build errors / warnings
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
greenkeeper[bot]
commented
7 years ago
Version 1.0.0 of mocha-webpack was just published.
The version 1.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of mocha-webpack.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v1.0.0Commits
The new version differs by 58 commits.
e7dd7b6Version 1.0.01083e32fix default value for webpack config (#186)e7d0f06add mocha4 support, use mocha4/webpack3 by default in development, re… (#179)fd26d21Version 1.0.0-rc.14b074e0use "unique" output path for bundle (#165)f6e202fRevert "Prefer memory-fs over real fs" (#164)fd0b032Version 1.0.0-rc.06d2fa5dPass env to webpack config via --webpack-env (#162)1db371dFix webpack 3 deprecation warnings (#161)198ca4aAllow absolute paths as entries (#160)6b834a1Fix loading symlinked webpack configuration. (#154)ab46bafPrefer memory-fs over real fs (#152)4004498Improve webpack config loading (#151)2a43227Support webpack config that exports a function (#141)b99a592Fix DeprecationWarning: loaderUtils.parseQuery() (#150)There are 58 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: