Fix for aux routes with empty base route

[VamsiVempati]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] angular.io application / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Navigating to an auxiallry route on a lazy loaded empty base route throws the following error:

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

#12842

Issue Number: #12842

export const routes: Routes = [
  {
    path: 'login',
    component: LoginModalComponent,
    outlet: 'modal'
  },
  {
    path: '',
    children: [
        {
            path: '',
            loadChildren: './Main/main.module#MainModule',
        },
    ]
  }
]

What is the new behavior?

Navigating to an auxiallry route on a lazy loaded empty base route does not throw any error and navigates successfully

Does this PR introduce a breaking change?

[ ] Yes
[x ] No

Other information

[maxime1992]

Encountered the bug with a lazy loaded module and an aux route, I tried to apply that directly into the node_modules folder and it didn't solve the issue.

It's true that it wasn't crashing anymore but the main outlet (the one with path: '') wasn't loaded at all.

On the other hand, I did the same test with the following PR and it worked perfectly: #25483

[atscott]

Closing as this doesn't fix the underlying problem. This change only prevents the error from occurring when attempting to activate the auxiliary route with loadChildren. The required fix would be to ensure the module is actually loaded in apply_redirects before proceeding to the next stage in the router.

[angular-automatic-lock-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.}