iSharkFly-Docs/angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-docs-cn/packages/router
History
Igor Minar 572fd7a79a build(ivy): remove the remains of ivy-jit mode (#27278) 
This stuff is obsolete and shouldn't be here because we removed the JIT mode on CI.

PR Close #27278
2018-11-27 10:30:58 -08:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
feat(router): add pathParamsChange mode for runGuardsAndResolvers (#26861)
2018-11-14 12:24:43 -08:00
test
build(ivy): remove the remains of ivy-jit mode (#27278)
2018-11-27 10:30:58 -08:00
testing
docs: update router to use @publicApi tags (#26595)
2018-10-19 14:35:53 -07:00
upgrade
build: remove ivy JIT mode (#26863)
2018-11-02 15:44:05 -07:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
test(ivy): mark failing test targets with fixme-ivy-jit and fixme-ivy-local tags (#26471)
2018-10-23 08:57:42 -07: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(ivy): run router tests with ivy on CI (#27195)
2018-11-21 09:19:40 -08:00
karma.conf.js
test(ivy): run router tests with ivy on CI (#27195)
2018-11-21 09:19:40 -08:00
LICENSE
docs(common): update copyright years (#21232)
2018-01-04 17:45:36 -05:00
package.json
build: update to rxjs@6.0.0 (#23679)
2018-05-03 10:53:39 -07:00
PACKAGE.md
docs: add package doc files (#26047)
2018-10-05 15:42:14 -07:00
public_api.ts
build: publish tree of files rather than FESMs (#18541)
2017-08-31 15:34:50 -07:00
README.md
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
rollup.config.js
feat(core): upgrade rxjs to 6.0.0-alpha.4 (#22573)
2018-03-19 21:51:51 -07:00
tsconfig-build.json
build: remove references to tsc-wrapped (#19298)
2017-09-21 13:55:52 -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