Solvedangular Lazy loaded module in named outlet throws error

[x] bug report
[ ] feature request
[ ] support request

Current behavior
Navigating to route with lazy loaded module in named outlet throws error:

Uncaught (in promise): TypeError: Cannot read property 'routes' of undefined

Expected behavior
Navigating to route with lazy loaded module in named outlet without errors.

Minimal reproduction of the problem with instructions
When I have configured my routes with named outlet and want to have lazy loaded module in that outlet.

export const routes: Routes = [
   path: '',
   component: AppComponent,
   children: [
       path: '',
       loadChildren: "app/home/home.module#HomeModule"
     },   {
       path: '',
       loadChildren: "app/about/about.module#AboutModule",
       outlet: "about"

Here is the plnkr to demonstrate the behavior:
(Anything is displayed because of error)

What is the motivation / use case for changing the behavior?
Using lazy loaded modules in named outlets.

Please tell us about your environment:

Angular version: 2.0.X

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Language: [all | TypeScript X.X | ES6/7 | ES5]

Node (for AoT issues): node --version =

28 Answers

✔️Accepted Answer

We have this

        path: 'me',
        outlet: 'hub',
        component: ProxyRouteComponent,
        children: [
                path: '',
                loadChildren: 'hub#HubModule',

Where proxy route component is simply

import { Component } from '@angular/core';

    selector: 'b-proxy-route',
    template: '<router-outlet></router-outlet>',
export class ProxyRouteComponent {

Other Answers:

Hi there, I am also interested to know if we will be able to lazy load secondary routes in the future

I know It's been a while since commit 8f2fa0f, but can you @vsavkin remember why you added that "a componentless route cannot have a named outlet set" guard.

Is it because it's just not possible to lazy load in such a way (because maybe router is designed so) or is this something that will eventually be resolved sometime.

Is there any information about this issue?? just so I know in my company if we should do a temporary solution until it's fixed or think about a more permanent solution. I just need an answer to a simple question:
"is this planned in the @angular/router team roadmap or not for now??"

Same issue here, I want to lazy load a module with a path to a named outlet. Cant figure a way to get it to work

More Issues: