Recursive loadChildren fails in 17, but worked in 16 about angular HOT 5 CLOSED

This seems likely to be an esbuild issue rather than anything to do with framework specifically. Note that your loadChildren does not have to be an import statement and in your case, there's no value in it since the file is already loaded. You can just change the loadChildren function to return the routes variable again: https://stackblitz.com/edit/stackblitz-starters-bgjmmw?file=src%2Frecursive.component.ts

@clydin Any additional thoughts here?

from angular.

Wow, I've never seen loadChildren without an import. Thanks for the solution.

I've been doing it my previous way for a few years and was surprised when it didn't work. I'll leave it up to y'all to decide if this is a real issue to fix.

from angular.

Wew it was introduce in angular 15 but esbuild broken lazyload

from angular.

As mentioned above, since the module is importing itself, there is no lazy loading in the recursive scenario. The ES module is already loaded and all members are available for direct access. There's no benefit to self importing. Circular imports are generally discourage as well. ES modules are also effectively singletons so the comment from the code of load another version of itself is technically not correct either.
However, while this does appear to be a defect in the bundler, this will most likely remain a low-priority defect as there appears to be no real world use case for this construct.

from angular.

Thanks @clydin. I’m going to closing this then as an issue with the bundler with an easy workaround.

from angular.