Closed dherges closed 3 years ago
Same problem
ERROR in Failed to list lazy routes: Unknown module '/angular8-new/web-v4/src/app/app.module#AppModule'. Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ โน ๏ฝขwdm๏ฝฃ: Failed to compile.
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:
platformBrowserDynamic(extraProviders).bootstrapModule(AppModule).catch(err => console.log(err));
If I comment the instruction the compilation works fine.
Obviously the app doesn't work.
My app refers AppModule only 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:
platformBrowserDynamic(extraProviders).bootstrapModule(AppModule)
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 ERROR in Failed to list lazy routes: '.../appModule#appModule'
i'm not understanding what is the problem and how to resolve it.
I fixed it by adding:
aot: true
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 tsconfig
path entries.
I updated the CLI and Errors got worse I have to go back to angular 8
Adding "aot": true
to architect.build.options in angular.json seems to have fixed it for me.
What I did:
- On main.ts comment the
platformBrowserDynamic(extraProviders).bootstrapModule(AppModule)
- Do the ng-serve and see the compiles erros, fix them
- Put the line on main.ts back and run the app
@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 AppModule
, likely due to some other diagnostic being produced. This happens before AppModule
can be registered with the NgModuleRouteAnalyzer
and thus AppModule
is unknown to listLazyRoutes
.
Transferring to the CLI repo as that's where the invocation of listLazyRoutes
occurs, which would fail before reporting the diagnostics.
Closing as string based lazy loading is no longer supported in version 12.
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.
๐ bug report
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:
๐ฌ Minimal Reproduction
Code: https://github.com/sparkles-dev/sparkles/pull/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
ReframedModule
would useprovideRoutes
from@angular/router
to hook a route definition into an app. It would then useANALYZE_FOR_ENTRY_COMPONENTS
from@angular/core
to 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-now
would result inGuestComponent
being rendered (for the wildcard route), which in turn would pick upPlayComponent
from the dynamic components API and render it to screen (viaComponentFactoryResolver
and friends).๐ฅ Exception or Error
see above. Detailed error from build logs:
build_3892_step_106_container_0.txt
๐ Your Environment
Related Issues
angular/angular#31032 angular/angular#31218 angular/angular#29363 angular/angular-cli#15546