honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Rafael 7c78282ce8 docs: fix typo in 'Routes' docs 2017-06-05 11:18:43 -07:00
..
scripts
…
src docs: fix typo in 'Routes' docs 2017-06-05 11:18:43 -07:00
test refactor(router): don't run the change detection every time an outlet is activated 2017-05-19 11:55:15 -07:00
testing build: import tslib rather than output TS helpers (#16901) 2017-05-23 14:01:39 -06:00
upgrade build: import tslib rather than output TS helpers (#16901) 2017-05-23 14:01:39 -06:00
.gitignore
…
LICENSE
…
README.md
…
index.ts
…
karma-test-shim.js test(router): enable running the campaign in non-ES6 browsers 2017-04-10 15:43:42 -07:00
karma.conf.js
…
package.json build: update router package.json placeholder (#17060) 2017-05-30 13:19:54 -07:00
public_api.ts
…
rollup.config.js build: import tslib rather than output TS helpers (#16901) 2017-05-23 14:01:39 -06:00
tsconfig-build.json fix(router): Update types for TypeScript nullability support 2017-04-18 12:07:33 -07:00

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