honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Marc Laval 46ce3317c3
test(router): enable running the campaign in non-ES6 browsers 
Closes #15806.
 		2017-04-10 15:43:42 -07:00
..
scripts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
src fix(router): the preloader use the module from the loaded config 2017-04-10 16:35:47 -06:00
test test(router): test preloading when a module is already loaded 2017-04-10 16:35:47 -06:00
testing test: add systemjs+umd integration test (#14196) 2017-03-19 12:23:07 -05:00
upgrade docs: in doc comments, replace [aA]ngular2 with Angular (#15463) 2017-03-27 09:44:35 -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: fix paths to typings files so tsickle resolves imports correctly 2017-03-16 17:34:29 -07:00
public_api.ts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
rollup.config.js test: add systemjs+umd integration test (#14196) 2017-03-19 12:23:07 -05:00
tsconfig-build.json build: fix file paths after moving modules/@angular/* to packages/* 2017-03-08 16:29:28 -08: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