RouterModule

class

npm Package	@angular/router
Module	import { RouterModule } from '@angular/router';
Source	router/src/router_module.ts

Overview

class RouterModule {
  constructor(guard: any, router: Router)
  static forRoot(routes: Routes, config?: ExtraOptions): ModuleWithProviders
  static forChild(routes: Routes): ModuleWithProviders
}

How To Use

RouterModule can be imported multiple times: once per lazily-loaded bundle. Since the router deals with a global shared resource--location, we cannot have more than one router service active.

That is why there are two ways to create the module: RouterModule.forRoot and RouterModule.forChild.

• forRoot creates a module that contains all the directives, the given routes, and the router service itself.
• forChild creates a module that contains all the directives and the given routes, but does not include the router service.

When registered at the root, the module should be used as follows

@NgModule({
  imports: [RouterModule.forRoot(ROUTES)]
})
class MyNgModule {}

For submodules and lazy loaded submodules the module should be used as follows:

@NgModule({
  imports: [RouterModule.forChild(ROUTES)]
})
class MyNgModule {}

Description

Managing state transitions is one of the hardest parts of building applications. This is especially true on the web, where you also need to ensure that the state is reflected in the URL. In addition, we often want to split applications into multiple bundles and load them on demand. Doing this transparently is not trivial.

The Angular router solves these problems. Using the router, you can declaratively specify application states, manage state transitions while taking care of the URL, and load bundles on demand.

Read this developer guide to get an overview of how the router should be used.

Static Members

Constructor

Annotations

@NgModule({ declarations: ROUTER_DIRECTIVES, exports: ROUTER_DIRECTIVES })