honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Yuan Gao 549f2254b4 refactor(core): remove getters for packages/animations, language-service, platform-browser, router (#19151) 
PR Close #19151
 		2017-09-20 12:38:37 -07:00
..
scripts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
src refactor(core): remove getters for packages/animations, language-service, platform-browser, router (#19151) 2017-09-20 12:38:37 -07:00
test feat(router): add ActivationStart/End events 2017-09-08 13:24:26 -04:00
testing build: roll up to named .js files rather than 'index.js' (#19190) 2017-09-19 16:59:18 -07:00
upgrade build: roll up to named .js files rather than 'index.js' (#19190) 2017-09-19 16:59:18 -07:00
.gitignore refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
LICENSE refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
README.md refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
index.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
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 build: build modules and examples for karma 2017-03-08 17:35:20 -08:00
package.json build: roll up to named .js files rather than 'index.js' (#19190) 2017-09-19 16:59:18 -07:00
public_api.ts build: publish tree of files rather than FESMs (#18541) 2017-08-31 15:34:50 -07:00
rollup.config.js build: roll up to named .js files rather than 'index.js' (#19190) 2017-09-19 16:59:18 -07:00
tsconfig-build.json build: roll up to named .js files rather than 'index.js' (#19190) 2017-09-19 16:59:18 -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