d0e72a8f8f
* docs(animations): fix links to `Component` animations * docs(core): fix links to `ReflectiveInjector` methods The `resolve` and other methods were moved from the `Injector` to the `ReflectiveInjector`. * docs(core): fix links to `Renderer` The local links were assuming that that methods were on the current document (e.g. `RootRenderer`), but they are actually on the `Renderer` class. * docs(router): fix links to methods * docs(forms): fix links to methods * docs(core): fix links to methods * docs(router): fix API page links and an internal link |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| test | ||
| testing | ||
| upgrade | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| index.ts | ||
| karma-test-shim.js | ||
| karma.conf.js | ||
| package.json | ||
| public_api.ts | ||
| rollup.config.js | ||
| tsconfig-build.json | ||
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.
Guide
Read the dev guide here.
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