AOT Build fails

[montella1507]

Windows 10,

Version: beta17 + @ngtools/webpack 1.1.0
ng build --aot=true

Log:
ENOENT: no such file or directory, stat 'v:\mediware\fixrepo\allimp-web\Source\Renewal\src\app\main\main.module'
Error: ENOENT: no such file or directory, stat 'v:\mediware\fixrepo\allimp-web\Source\Renewal\src\app\main\main.module'
at Error (native)
at Object.fs.statSync (fs.js:987:18)
at _symbolImportLookup (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules@ngtools\webpack\src\entry_resolver.js:103:28)
at Object.resolveEntryModuleFromMain (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules@ngtools\webpack\src\entry_resolver.js:148:18)
at AotPlugin._setupOptions (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules@ngtools\webpack\src\plugin.js:105:77)
at new AotPlugin (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules@ngtools\webpack\src\plugin.js:34:14)
at Object.exports.getWebpackAotConfigPartial (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\angular-cli\models\webpack-build-typescript.js:57:13)
at new NgCliWebpackConfig (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\angular-cli\models\webpack-config.js:18:42)
at Class.run (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\angular-cli\tasks\build-webpack.js:17:22)
at Class.run (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\angular-cli\commands\build.js:50:26)
at Class. (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\angular-cli\lib\models\command.js:152:17)
at tryCatch (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\rsvp\dist\lib\rsvp-internal.js:215:12)
at invokeCallback (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\rsvp\dist\lib\rsvp-internal.js:230:13)
at v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\rsvp\dist\lib\rsvp\then.js:29:16
at flush (v:\mediware\fixrepo\allimp-web\Source\Renewal\node_modules\rsvp\dist\lib\rsvp\asap.js:85:5)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)

All of the mentioned files exist

[Meligy]

Can you please create a repository that shows the problem?

I have AoT issues shown here:
https://github.com/meligy/routing-angular-cli

But it's browser issues not build issues.

[montella1507]

Ah i think i have fixed the problem and its super silly....

Not working:
//main.ts import { MainModule } from './app/main/main.module' //point to main.module.ts;

Working:
//main.ts import { MainModule } from './app/main' //point to index.ts with export * from "./main.module".

[Meligy]

So, did you get AoT to work for you completely?

If so, can you please share how your app routes look like?

Thanks.

[montella1507]

Well.. it has nothing to do with routing... it is build process. There must be a bug in Path resolution in the build process.

If i use index.ts (barel file) it works, if i import main module directly:

import { MainModule } from './main/main.module';
it doesnt.

HOW TO SIMULATE:

1. create new app with ng new
2. change
   import { AppModule } from './app';

to
import { AppModule } from './app/app.module';
in main.ts

[Meligy]

I get that. I mean. Are you able to serve the app in the browser now with aot?

Something like:

ng serve --aot

Without errors in browser console?

[montella1507]

Yeah it works. I just had to remove ViewEncapsulation.None, because AOT has problems with that. But it works perfectly.

[montella1507]

ah it looks i have very similar problem to this ##2577
but different way how to simulate

[filipesilva]

Dupe of #2577 I think. The same root cause at least. I'll close this one in favor of that, it here more info on it. I'll add your repro steps there as well.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}