I've been battling this error (supposedly related to AOT) even using the newer templates that don't have the include: '/ClientApp' in the webpack.config.js. Here are my steps for reproducing it:
dotnet new angularnpm install
webpack --config .\webpack.config.vendor.js --env.prod
webpack --env.prodERROR in ./ClientApp/boot.server.ts
Module not found: Error: Can't resolve './../$$_gendir/ClientApp/app/app.server.module.ngfactory' in 'C:\Users\xxxxx\DocumentsVisual Studio 2017\Projects\testapp2\ClientApp'
@ ./ClientApp/boot.server.ts 8:0-94
ERROR in Error: Please update @angular/cli. Angular 5+ requires at least Angular CLI 1.5+
at throwNotSupportedError (C:\Users\xxx\Documents\Visual Studio 2017\Projects\testapp2\packages\compiler-cli\src\ngtools_api.ts:132:9)
at Function.NgTools_InternalApi_NG_2.codeGen (C:\Users\xxx\Documents\Visual Studio 2017\Projects\testapp2\packages\compiler-cli\src\ngtools_api.ts:80:11)
at _donePromise.Promise.resolve.then (C:\Users\xxx\Documents\Visual Studio 2017\Projects\testapp2\node_modules\@ngtools\webpack\src\plugin.js:428:58)
at process._tickCallback (internal/process/next_tick.js:109:7)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:393:7)
at startup (bootstrap_node.js:150:9)
at bootstrap_node.js:508:3
Once the error starts, even reverting changes won't make it go away.
I believe I found what corrects this. In webpack.config.js, change line 4 from:
const AotPlugin = require('@ngtools/webpack').AotPlugin;
to
const AotPlugin = require('@ngtools/webpack').AngularCompilerPlugin;
I can verify that this resolved one issue I was having and if you're upgrading to Angular 5, it appears it's a necessity.
Here is a reference https://github.com/NativeScript/nativescript-dev-webpack/issues/312
End result to fix everything was to disable server side rendering. :-(
Most helpful comment
I believe I found what corrects this. In webpack.config.js, change line 4 from:
const AotPlugin = require('@ngtools/webpack').AotPlugin;to
const AotPlugin = require('@ngtools/webpack').AngularCompilerPlugin;I can verify that this resolved one issue I was having and if you're upgrading to Angular 5, it appears it's a necessity.