'RouterModule.forRoot called twice
I am trying to implement Lazy Loading into my application but seem to be coming across an issue whereby I get the error message :
Error: RouterModule.forRoot() called twice. Lazy loaded modules should use RouterModule.forChild() instead.
So I have my main app-routing.module.ts and also app-module.ts which looks like below:
app-module.ts
// External Dependencies
import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { HttpClientModule } from '@angular/common/http';
import { FormsModule, ReactiveFormsModule } from '@angular/forms';
import { BrowserAnimationsModule } from '@angular/platform-browser/animations';
// Internal Dependencies
import { MaterialModule } from '../app/configuration/material/material.module';
import { SharedModule } from '../app/application/shared/shared.module';
import { RoutingModule } from '../app/configuration/routing/routing.module';
import { SettingsModule } from '../app/application/settings/settings.module';
import { AppComponent } from './app.component';
import { SearchService } from './application/shared/services/search.service';
@NgModule({
declarations: [AppComponent],
imports: [
BrowserAnimationsModule,
BrowserModule,
SharedModule,
RoutingModule,
MaterialModule,
HttpClientModule,
FormsModule,
],
providers: [ ],
bootstrap: [AppComponent]
})
export class AppModule { }
app-routing.ts
// External Dependencies
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { RouterModule, Routes } from '@angular/router';
import { HttpModule } from '@angular/http';
const appRoutes: Routes = [
{ path: '', redirectTo: 'overview', pathMatch: 'full' },
{ path: 'overview', loadChildren: '../../application/overview/overview.module#OverviewModule' },
{ path: 'search', loadChildren: '../../application/search/search.module#SearchModule' },
{ path: 'policy/:id', loadChildren: '../../application/policy/policy.module#PolicyModule' },
{ path: 'claim/:id', loadChildren: '../../application/claim/claim.module#ClaimModule' },
{ path: 'settings', loadChildren: '../../application/settings/settings.module#SettingsModule' }
];
@NgModule({
imports: [
CommonModule,
RouterModule.forRoot(appRoutes)
],
exports: [
RouterModule
],
declarations: []
})
export class RoutingModule { }
This works fine and the application correctly loads. The issue from here is that in the SharedModule it has come components to redirect the user using routerLink to a new page.
shared.module.ts
// External Dependencies
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
import { FormsModule, ReactiveFormsModule } from '@angular/forms';
import { CalendarModule } from 'primeng/calendar';
import { AgmCoreModule } from '@agm/core';
import { FroalaEditorModule, FroalaViewModule } from 'angular-froala-wysiwyg';
import { PdfViewerModule } from 'ng2-pdf-viewer';
// Internal Dependencies
import { MaterialModule } from '../../configuration/material/material.module';
import { RoutingModule } from '../../configuration/routing/routing.module';
import { NavbarTopComponent } from '../../application/shared/components/navbar-top/navbar-top.component';
import { NavbarSideComponent } from './components/navbar-side/navbar-side.component';
import { TemplateCardWComponent } from './components/template-card-w/template-card-w.component';
import { FilterPipe } from './pipes/filter.pipe';
import { StandardTableComponent } from './components/standard-table/standard-table.component';
import { OrderPipe } from '../shared/pipes/order.pipe';
import { ActionComponent } from './components/action/action.component';
import { GoogleMapComponent } from './components/google-map/google-map.component';
import { HtmlEditorComponent } from './components/html-editor/html-editor.component';
import { PdfViewerComponent } from './components/pdf-viewer/pdf-viewer.component';
import { KeyBindingPipe } from './pipes/key-binding.pipe';
import { StandardEditTableComponent } from './components/standard-edit-table/standard-edit-table.component';
@NgModule({
imports: [
CommonModule,
MaterialModule,
RoutingModule,
FormsModule,
CalendarModule,
AgmCoreModule,
FroalaEditorModule,
FroalaViewModule,
PdfViewerModule
],
declarations: [
NavbarTopComponent,
NavbarSideComponent,
TemplateCardWComponent,
FilterPipe,
StandardTableComponent,
OrderPipe,
ActionComponent,
GoogleMapComponent,
HtmlEditorComponent,
PdfViewerComponent,
KeyBindingPipe,
StandardEditTableComponent
],
exports: [
]
})
export class SharedModule { }
As you can see I am having to import the RouterModule. If I remove the RouterModule, the application will load but no re-direct. If I keep the RouterModule the application will cause the error at the top of the question.
Could anyone help me on this.
Solution 1:[1]
I got this error because I somehow accidentally imported the root AppModule
into my lazy-loaded module. This caused the root AppRoutingModule
to be called again when the lazy-loaded module was loaded, and thus RouterModule.forRoot
was called twice.
If you are certain you aren't calling RouterModule.forRoot
twice then this could be the cause of the issue. Check that you aren't importing any modules in your lazy-loaded module that direcly call RouterModule.forRoot
or import a module that calls RouterModule.forRoot
.
Solution 2:[2]
I've been struggling with this for a while. Finally found the issue.
I'm using lazy loading. And even though I'd only used .forRoot in one place in the app, the error suggested that I was using it twice.
Turned out that I was importing the AppRoutingModule from app.routing.ts file in one of the feature modules that was being lazy loaded. And I had done this earlier because it kept saying it didn't recognize routerLink which I had used in one of the components in that feature module.
The solution was to replace the AppRoutingModule import in the feature module with an import of the RouterModule from '@angular/router'. Now everything works.
PS - when I say feature module, I mean sub module that I'm lazy loading.
Solution 3:[3]
I have faced the problem too, and for the future comers, This is my solution.
Do not import AppRoutingModule in oer module, Import RoutingModule
It will be solved. Here is an example.
import { RouterModule } from '@angular/router';
And in the imports array
@NgModule({
declaration: [], // your contents
imports: [
RouterModule,
// Other modules
]
})
Solution 4:[4]
In your separate lazily loaded modules, OverviewModule, SearchModule, PolicyModule, ClaimModule and SettingsModule do you have routes declared in them? If so, in the @NgModule of each do you have a RouterModule.forRoot() somewhere? They should be RouterModule.forChild(...). It sounds like that could be the issue.
Solution 5:[5]
instead of using
imports: [
CommonModule,
RouterModule.forRoot(appRoutes)
],
use
imports: [
CommonModule,
RouterModule.forChild(appRoutes)
],
Solution 6:[6]
Convert the routing module from
@NgModule({
imports: [RouterModule.forRoot(routes)],
exports: [RouterModule]
})
to
@NgModule({
imports: [RouterModule.forChild(routes)],
exports: [RouterModule]
})
that will solve the error
Solution 7:[7]
I got this error when I mistakenly named the route module of my lazy loaded module AppRoutingModule.
I renamed to match the module name eg StockRoutingModule and it was fixed.
Solution 8:[8]
I know this is an old post but I recently encountered this issue because I was unknowingly importing AppModule
into a child module.
My IDE had I pop-up I clicked unintentionally and that added AppModule
to my imports. Something to search for if you encounter this problem!
Solution 9:[9]
Use RouterModule.forChild(routes)
inside child module. Like this file ../../application/overview/overview.module
.
If you have more child modules then use RouterModule.forChild(yourarray)
instead of RouterModule.forRoot(yourarray)
Solution 10:[10]
I've faced this issue because I use RouterModule.forRoot(myRoutes)
inside my child module which I lazy-loaded. It should've been
@NgModule({
imports: [ RouterModule.forChild(myRoutes) ], // changed forRoot with forChild
exports: [ RouterModule ]
})
Solution 11:[11]
You don't import RouterModule
into your SharedModule
. You import RoutingModule
there. And this module imports RouterModule
with forRoot
which is called second time when lazy loading it. This causes the error.
Instead you should import RouterModule
directly if you need redirects.
shared.module.ts
@NgModule({
imports: [
CommonModule,
MaterialModule,
RouterModule, /* NOT RoutingModule */
FormsModule,
CalendarModule,
AgmCoreModule,
FroalaEditorModule,
FroalaViewModule,
PdfViewerModule
],
Solution 12:[12]
I was also facing the same while using lazy loading. Finally i have found some solution.
I have removed "routingModule" and "routerModule" from sharedModule and using routerModule only in respective routing.module.ts file.
Solution 13:[13]
In my case the issue was that I had forgotten to add the type when declaring my routes array in the feature module, If you have made sure that forRoot is not called twice and neither is AppRoutingModule imported multiple times you can check for basic mistakes like the one I made.
It was defined as:
const feature_routes = [.....];
instead of:
const feature_routes : Routes = [.....];
Solution 14:[14]
In my case I used forRoot(routes) in App Modules and all other modules as well.
To get rid of this error I just put forRoot(route) in App module and changed all other modules to forChild(routes).
That's it. It works for me amazingly!
Solution 15:[15]
I think I've got the solution to this problem.
In the shared.module.ts
file you added RoutingModule
to the array of imports and again in the app.module.ts
file you imported both the SharedModule
(which already contains the RoutingModule
) and the RoutingModule
.
Simply remove the RoutingModule from the imports:
array in the shared.module.ts
file.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow