lazy loading chunks not built if bootstrap is not in main.ts file

[devversion]

Currently if people want to use lazy loading within Angular CLI projects and their bootstrap code is not placed inside of the $PROJECT_ROOT/main.ts file, the chunks for the lazy-loading module are not being generated.

This leads to JIT runtime errors that indicate that the lazy module couldn't be found.

core.js:1673 ERROR Error: Uncaught (in promise): Error: Cannot find module 'lazy/slider.module'
Error: Cannot find module 'lazy/slider.module'
    at $_lazy_route_resource lazy namespace object:5

Moving the boostrap call to the main.ts file fixes this issue (credits to @filipesilva for this finding)

--

It would be good to have some warning or note that implicates that lazy modules won't be detected if the bootstrap call is placed somewhere else.

Issue demonstration: https://github.com/DevVersion/lazy-load-test-cli

cc. @filipesilva

[santiago-elustondo]

Is there a workaround? I need to call bootstrapModule() in a different file.

[mascarenhas]

You can get around this by adding an entryModule key in the application's angularCompilerOptions object in the tsconfig.json file pointing to your main module, like this: "entryModule": "./app/app.module#AppModule".

That this is failing at runtime instead of throwing a compiler error is probably a bug in the Angular CLI, the relevant function in the Angular CLI source is bailing out with null in some cases (

angular-cli/packages/ngtools/webpack/src/entry_resolver.ts

Line 155 in b403aa6

if (bootstrap.length != 1) {

) and throwing an error in others.

[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.}