angular-cn/packages/router/README.md

Angular Router
=========

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 isn’t trivial.

The Angular router is designed to solve these problems. Using the router, you can declaratively specify application state, manage state transitions while taking care of the URL, and load components on demand.

## Overview
Read the overview of the Router [here](https://vsavkin.com/angular-2-router-d9e30599f9ea).

## Guide
Read the dev guide [here](https://angular.io/docs/ts/latest/guide/router.html).

## Local development

```
# keep @angular/router fresh
$ ./scripts/karma.sh

# keep @angular/core fresh
$ ../../../node_modules/.bin/tsc -p modules --emitDecoratorMetadata -w

# start karma
$ ./scripts/karma.sh
```
-												chore(README): fix a typo

											
										
										
											2016-06-17 12:19:10 -04:00
+								Angular Router
-												docs(router): add a README to include a link to the guide

											
										
										
											2016-06-17 12:17:48 -04:00
+								=========
-												docs(router): add a README

											
										
										
											2016-06-09 17:57:50 -04:00
 								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 isn’t trivial.
-												docs(router): add a README to include a link to the guide

											
										
										
											2016-06-17 12:17:48 -04:00
+								The Angular router is designed to solve these problems. Using the router, you can declaratively specify application state, manage state transitions while taking care of the URL, and load components on demand.
-												docs(router): add a README

											
										
										
											2016-06-09 17:57:50 -04:00
-												docs(router): add a README to include a link to the guide

											
										
										
											2016-06-17 12:17:48 -04:00
+								## Overview
-												docs(router): fix broken link (#14431)

Closes #14430
											
										
										
											2017-02-16 14:32:17 -05:00
+								Read the overview of the Router [here](https://vsavkin.com/angular-2-router-d9e30599f9ea).
-												docs(router): add a README to include a link to the guide

											
										
										
											2016-06-17 12:17:48 -04:00
 								## Guide
-												refactor(core): change module semantics

This contains major changes to the compiler, bootstrap of the platforms
and test environment initialization.

Main part of #10043
Closes #10164

BREAKING CHANGE:
- Semantics and name of `@AppModule` (now `@NgModule`) changed quite a bit.
  This is actually not breaking as `@AppModules` were not part of rc.4.
  We will have detailed docs on `@NgModule` separately.
- `coreLoadAndBootstrap` and `coreBootstrap` can't be used any more (without migration support).
  Use `bootstrapModule` / `bootstrapModuleFactory` instead.
- All Components listed in routes have to be part of the `declarations` of an NgModule.
  Either directly on the bootstrap module / lazy loaded module, or in an NgModule imported by them.

											
										
										
											2016-07-18 06:50:31 -04:00
+								Read the dev guide [here](https://angular.io/docs/ts/latest/guide/router.html).
 								## Local development
 								```
 								# keep @angular/router fresh
 								$ ./scripts/karma.sh
 								# keep @angular/core fresh
 								$ ../../../node_modules/.bin/tsc -p modules --emitDecoratorMetadata -w
 								# start karma
 								$ ./scripts/karma.sh
 								```