Tiago Melo

@MartoYankov So, in my previous configuration I had modal pages lazy-loaded with the following configuration: ``` // app.module.ts { path: 'login', outlet: 'loginModal', loadChildren: './login/login.module#LoginModule } ``` ``` // login.module.ts...

Makes sense it doesn't work like that. I didn't know Angular added a `router-outlet` in that case. It must do that to handle both `children` and `loadChildren` since the behaviour...