Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upFailed to list lazy routes: Unknown module –– INCL. REPRO #18151
Comments
|
Same problem ERROR in Failed to list lazy routes: Unknown module '/angular8-new/web-v4/src/app/app.module#AppModule'. |
|
Any news? This is a blocking issue migrating to Ivy! |
|
I don't think this is Angular's bug, this is a bug related to library authors who dont respect the Angular Library Spec and implement their own build pipelines. In my case it was auth0' angular jwt, i submitted a pr to fix it on their repo la a month ago, still isn't merged |
|
I have not libraries in my project and I have the same error. I updated from version 8 and I have this problem. With "enableIvy: false" the error disappears. |
|
In my project, it seems to be related to the following instruction in main.ts: |
|
Good point @notarnet in my case I´m using ng-packagr .. so this was a litrle confusing Seems that the angular is not passing compiling erros from the app to this main.ts What I did:
Maybe this issue can be something to fix on angular build to guarantee that the compile errors is always displayed on the console |
|
@mariohmol 's workaround helped |
|
I was running my program last week without error and today without any changes i got this error i'm not understanding what is the problem and how to resolve it. |
|
hey anyone got the solution for it. I am facing same issue while updating ng 8 to ng 9 |
|
I solved this by updating the Angular CLI to the latest version and restarting my terminal. The CLI seemed to have issues with relative |
|
I updated the CLI and Errors got worse I have to go back to angular 8 |
|
Adding |
@mariohmol I commented those lines, there were no compilation errors, so I uncommented the lines back and it simply worked. WTF? |
|
@kinging123 akakakkakakak thats weird.. but I guess there is some caching files in the build process, and that way you forced the compiler to do all over again (guess =) ) |
|
The error mode here seems to be that the compiler fails analysis of |
|
Transferring to the CLI repo as that's where the invocation of |

Affected Package
Updatimg from 9.0.0-next.2 to 9.0.0-next.4
Is this a regression?
Chances are: no.
Description
ng build fails with:
Code: sparkles-dev/sparkles#533
Build logs: https://circleci.com/gh/sparkles-dev/sparkles/3892?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
Application
Library
How It Worked (before <= next.2)
The lib
ReframedModulewould useprovideRoutesfrom@angular/routerto hook a route definition into an app. It would then useANALYZE_FOR_ENTRY_COMPONENTSfrom@angular/coreto add dynamic components to an app.At app runtime, the module would use the
external/**route definition to pick a dynamic component and render it for a wildcard route. For example,#/external/play-it-nowwould result inGuestComponentbeing rendered (for the wildcard route), which in turn would pick upPlayComponentfrom the dynamic components API and render it to screen (viaComponentFactoryResolverand friends).see above. Detailed error from build logs:
build_3892_step_106_container_0.txt
Related Issues
angular/angular#31032
angular/angular#31218
angular/angular#29363
#15546