As webpack inches closer and closer to 2, uptake is increasing due to the awesome new native ES6 support. In webpack 2.1.0-beta.22 and below, older configurations were still supported, but since beta.23 the new schema is now enforced and wallaby-webpack completely breaks as a result.
The primary issue has seems to be due to webpack-wallaby's use of resolve.modulesDirectories, which has been deprecated along with resolve.root and resolve.fallback to a single option: modules: string[]. See the migration docs for additional info.
If you accept PRs I can implement something that fixes this.
As webpack inches closer and closer to 2, uptake is increasing due to the awesome new native ES6 support. In webpack 2.1.0-beta.22 and below, older configurations were still supported, but since beta.23 the new schema is now enforced and wallaby-webpack completely breaks as a result.
The primary issue has seems to be due to webpack-wallaby's use of
resolve.modulesDirectories
, which has been deprecated along withresolve.root
andresolve.fallback
to a single option:modules: string[]
. See the migration docs for additional info.If you accept PRs I can implement something that fixes this.