46b212706b
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.
26 lines
978 B
Markdown
26 lines
978 B
Markdown
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](http://victorsavkin.com/post/145672529346/angular-router).
|
||
|
||
## 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
|
||
```
|