ExtWebpackPlugin: Incorrectly assumes `index.html` in use

[shieldsjared]

Using app.json, you can disable/change the page output path. Recent changes to ExtWebpackPlugin incorrectly assume that index.html is in use, and the process bombs if it is not...

Error: ENOENT: no such file or directory, lstat 'D:\XXX\clients\admin\build\production\index.html'
    at Object.fs.lstatSync (fs.js:941:11)
    at replacizeFileSync (D:\XXX\clients\admin\node_modules\replace\replace.js:140:22)
    at module.exports (D:\XXX\clients\admin\node_modules\replace\replace.js:80:17)
    at ExtWebpackPlugin.postBuildProcess (D:\XXX\clients\admin\node_modules\@sencha\ext-webpack-plugin\dist\index.js:114:9)
    at compiler.hooks.done.tap.stats (D:\XXX\clients\admin\node_modules\@sencha\ext-webpack-plugin\dist\index.js:88:12)
    at AsyncSeriesHook.eval [as callAsync] (eval at create (D:\XXX\clients\admin\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:9:1)
    at AsyncSeriesHook.lazyCompileHook (D:\XXX\clients\admin\node_modules\tapable\lib\Hook.js:154:20)

app.json snippet

"output": {
    "base": "${workspace.build.dir}/${build.environment}",
    "page": {
      "path": "../../../../Views/Admin/Index.cshtml",
      "enable": false
    },
}