Navigating to named router-outlet with 'null' does not work from within named router-outlet · Issue #36766 · angular/angular · GitHub
![Angular 2 Named Outlet: Uncaught (in promise): Error: Cannot match any routes. URL Segment: - Stack Overflow Angular 2 Named Outlet: Uncaught (in promise): Error: Cannot match any routes. URL Segment: - Stack Overflow](https://i.stack.imgur.com/GT1Yn.jpg)
Angular 2 Named Outlet: Uncaught (in promise): Error: Cannot match any routes. URL Segment: - Stack Overflow
Deborah Kurata on Twitter: "Turned in M9 of "Angular Routing" for @pluralsight. It's on secondary routes with named router outlets (in green). #Angular https://t.co/Y854GSO1M0" / Twitter
![Lazy-Loading Router-Outlets: Named Router Outlets in Angular (Auxiliary Routes) | by Pradeep Singh Rawat | Time Machine | Medium Lazy-Loading Router-Outlets: Named Router Outlets in Angular (Auxiliary Routes) | by Pradeep Singh Rawat | Time Machine | Medium](https://miro.medium.com/max/1352/1*eqzv2nKlKbbJEE7uKFuZpQ.jpeg)