Routing to sub routing module without lazy loading

Question

I want to have multiple routing modules in order to keep my application clean and easy to read. I currently use lazy loading for the SubComponent but I don't want to do this. So I am looking for a way to change this. Anyways, here is the currently working code.

I have the following two routing files.

app-routing.module.ts:

import { NgModule } from '@angular/core';
import { Routes, RouterModule } from '@angular/router';

const routes: Routes = [
  { path: '', component: HomeComponent },
  { path: 'sub', loadChildren: './sub/sub.module#SubModule' }
];

@NgModule({
  imports: [RouterModule.forRoot(routes)],
  exports: [RouterModule]
})

sub-routing.module.ts:

import { NgModule } from '@angular/core';
import { Routes, RouterModule } from '@angular/router';

const routes: Routes = [
  { path: '', component: SubComponent, children: [
    { path: 'new', component: SubEditComponent }
  ] },
];

@NgModule({
  imports: [RouterModule.forChild(routes)],
  exports: [RouterModule]
})

It works fine this way but I don't want to apply lazy loading to this SubComponent. So, ideally I want to change the app-routing.module.ts to this:

import { NgModule } from '@angular/core';
import { Routes, RouterModule } from '@angular/router';

const routes: Routes = [
  { path: '', component: HomeComponent },
  { path: 'sub', component: SubComponent }
];

@NgModule({
  imports: [RouterModule.forRoot(routes)],
  exports: [RouterModule]
})

This will not work and result in the following error:

ERROR Error: Uncaught (in promise): Error: Cannot match any routes. URL Segment: 'sub/new'
Error: Cannot match any routes. URL Segment: 'sub/new'

The SubComponent will grow substantially in size and I don't want to apply lazy loading for my own reasons. So in any event, is there a way to use multiple routing files while avoiding lazy loading?

Emin Laletovic · Accepted Answer · 2017-08-01 20:29:20Z

25

Have you tried loading it like this:

{ path: 'sub', loadChildren: () => SubModule }

You can find a lot more details here.

answered Aug 1, 2017 at 20:29

Emin Laletovic

4,3541 gold badge17 silver badges26 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Spurious Over a year ago

Thanks, I will have a read through this and try your solution tomorrow. Will keep you posted and upvote if it works.

Ben Over a year ago

This will disable the lazy loading feature.

Mickey Sly Over a year ago

It works on recompile but i get syntax errors when building or re-running the app. How do you get past this error: ERROR in Cannot read property 'loadChildren' of undefined

MiKr13 Over a year ago

Please note, this solution can cause issues in a Production build. The error will be: ERROR: Runtime Compiler is Not Loaded or something like that. reference: Github Stack-Overflow

yurzui · Accepted Answer · 2017-08-03 10:44:52Z

7

You forgot to declare child route to new

const routes: Routes = [
  { path: '', component: HomeComponent },
  { 
    path: 'sub', 
    component: SubComponent,
    children: [
      { path: 'new', component: SubEditComponent }
    ] 
  }
];

if you want to keep the second routing module then

sub-routing.module.ts

const routes: Routes = [
  { path: 'sub', component: SubComponent, children: [
    { path: 'new', component: SubEditComponent }
  ] },
];

sub.module.ts

@NgModule({
  ...
  imports: [
   ...
   SubRoutingModule,

app.module.ts

@NgModule({

  imports: [
    ...,
    AppRoutingModule,
    SubModule

Plunker Example

edited Aug 3, 2017 at 10:44

answered Aug 1, 2017 at 20:29

yurzui

215k32 gold badges450 silver badges413 bronze badges

4 Comments

Spurious Over a year ago

It would make the second routing module obsolete - something I explicitly want to avoid.

Spurious Over a year ago

Thanks for your edit but the imports already exist and it does not work.

yurzui Over a year ago

@Spurious I think you forgot to change { path: '', component: SubComponent to { path: 'sub', component: SubComponent in sub-routing.module.ts

Chris Haines Over a year ago

This is the correct answer that works for prod (AOT) builds. To summarise, import the submodule into AppModule, and put the routes only in the submodule. No need for any route entries in AppModule for the submodule routes.

HungNM2 · Accepted Answer · 2021-03-21 14:25:29Z

0

app.module.ts

 @NgModule({
    
      imports: [
        ...,
       SubModule,   /* subModule with routing, the order is very important */ 
       AppRoutingModule,  // put it at the end
      ]
}

the order of routing Modules is very important.

AppRoutingModule.ts

const routes: Routes = [
  // filter path '**' will prevent routing to the subModule
  { path: '**', component: PageNotFoundComponent },
];

answered Mar 21, 2021 at 14:25

HungNM2

3,4651 gold badge35 silver badges21 bronze badges

Comments

Luis Felipe Maccheri de Toledo · Accepted Answer · 2018-03-09 19:24:07Z

-3

You can use an arrow function as eminlala said, but it won't work if you run a prod build.

{ path: 'sub', loadChildren: () => SubModule }

So, in order to make it work in a prod build, you need to create an export function as follows.

import SubModule from 'path-to-sub-module';

export function loadSubModule() {
  return SubModule;
}

export const SUB_MODULE_ROUTING = {
  path: 'sub',
  loadChildren: loadSubModule,
};

I use to create a file with this conf and import it to the AppRoutingModule, but you can write it inside AppRoutingModule.

I hope it helps.

answered Mar 9, 2018 at 19:24

Luis Felipe Maccheri de Toledo

11 bronze badge

1 Comment

Chris Haines Over a year ago

The suggested solution makes no difference whatsoever to prod builds.

Collectives™ on Stack Overflow

Routing to sub routing module without lazy loading

4 Answers 4

4 Comments

4 Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

4 Comments

4 Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related