Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Component loaded via lazy module is not rendering inside named outlet, but outlet is activated correctly

See original GitHub issue

Which @angular/* package(s) are the source of the bug?

router

Is this a regression?

Yes

Description

I swear this used to work in Angular 13.2.2

See README.md in repo

No Router errors when tracing enabled

Please provide a link to a minimal reproduction of the bug

https://github.com/johngrimsey/router-debug

Please provide the exception or error you saw

No response

Please provide the environment you discovered this bug in (run `ng version`)

No response

Anything else?

Haven’t been able to check in Angular 13.2.2 - but my expectation is that the component should be rendered

Issue Analytics

State:
Created a year ago
Comments:9 (3 by maintainers)

Top GitHub Comments

1reaction

atscottcommented, Aug 1, 2022

Similar to https://github.com/angular/angular/issues/46500, your application has broken the parent/child relationship of the router outlets. The RouterOutlet in the dialog needs to be a logical child in the element injector tree of the parent.

Closing as an issue outside of Angular.

0reactions

angular-automatic-lock-bot[bot]commented, Sep 9, 2022

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

Top Results From Across the Web

Angular 4 Lazy loading with named router-outlet not working

The workaround or we can say solution to this issue is, use non-empty paths for your top level routes if auxilary(i.e. named) routes...

Lazy loaded module in named outlet throws error · Issue #12842

have anyone find a temporary workaround for this issue? (goal is to load component in named outlets lazily).

Lazy-loading feature modules - Angular

To lazy load Angular modules, use loadChildren (instead of component ) in your AppRoutingModule routes configuration as follows. AppRoutingModule (excerpt)

Angular Navigation: How Routing & Redirects Work in Angular ...

Lazy loading routes. Now the current way our routes are setup makes it so they are included in the same chunk as the...

Angular Routing Guide: How to optimize app navigation

The key to successful Angular apps is easily navigable pages with routing. Today, we'll learn how to use Angular Router's capabilities.