honeymoose
/
angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Lars Gyrup Brink Nielsen c67bad4f43 docs(router): minor typo (#18226) 
Fix a minor typo in the description of a router spec.
 		2017-07-20 09:32:34 -07:00
..
scripts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
src fix(router): terminal route in custom matcher 2017-07-18 10:25:18 -07:00
test docs(router): minor typo (#18226) 2017-07-20 09:32:34 -07:00
testing build: import tslib rather than output TS helpers (#16901) 2017-05-23 14:01:39 -06:00
upgrade fix(router): encode URLs the same way AngularJS did (closer to spec) (#17890) 2017-07-06 17:10:25 -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 fix(router): fix outdated homepage url in NPM package (#17899) 2017-07-11 12:00:56 -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 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