honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/modules/@angular/router
History
Miško Hevery 979657989b fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
..
scripts chore(router): changes the router setup to align with other modules 2016-06-21 12:17:30 -07:00
src fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
test fix(router): support guards navigating synchronously (#11150) 2016-08-29 17:51:38 -07:00
testing fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
.gitignore chore(router): update config before publishing to npm 2016-06-21 12:17:30 -07:00
CHANGELOG.md chore(router): update changelog 2016-08-09 11:02:04 -07:00
LICENSE chore: set up test and build infrastructure 2016-06-21 12:17:30 -07:00
README.md refactor(core): change module semantics 2016-07-26 07:04:10 -07:00
index.ts fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
karma-test-shim.js fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
karma.conf.js chore(dependencies): switch from es6-shim to core-js (#10884) 2016-08-25 17:28:36 -07:00
package.json fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
rollup-testing.config.js fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
rollup.config.js fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
tsconfig-testing.json fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -07:00
tsconfig.json fix(packages): use ES modules for primary build (#11120) 2016-08-30 18:07:40 -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