Exception using dynamic module in wildcard route (**)

I’m submitting a … (check one with “x”)

[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior If I try to load a dynamic Module as wildcard, I get a null pointer exception:

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { RouterModule } from '@angular/router';

import { AppComponent } from './app.component';

@NgModule({
    imports: [
        BrowserModule,
        RouterModule.forRoot([
                        { path: '', redirectTo: 'login', pathMatch: 'full' },
            { path: 'login', loadChildren: 'app/login/login.module#LoginModule' },
            { path: 'not-found', loadChildren: 'app/not-found/not-found.module#NotFoundModule' },
            { path: '**', redirectTo: 'not-found', pathMatch: 'full' }
        ])
    ],
    declarations: [
        AppComponent
    ],
    bootstrap: [AppComponent]
})
export class AppModule { }

This is the error I get: handleError — core.umd.js:3370EXCEPTION: Uncaught (in promise): TypeError: undefined is not an object (evaluating 'route._loadedConfig.routes')

Minimal reproduction of the problem with instructions Here you can find a ready project

• Angular version: 2.0.1
• Browser: [all]
• Language: [all]
• Node (for AoT issues): node --version = 6.6

[tskweres]

I am still unable to lazyload wildcard “**” routes in Angular 4.x, is this fixed somewhere?

[angular-automatic-lock-bot[bot]]

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