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 44de10e2db feat: mark angular packages as side-effect free (#22785) 
This flag is picked up by webpack v4 and used for more agressive optimizations.

Our code is already side-effect free, because that's what we needed for build-optimizer to work.

PR Close #22785
2018-03-15 14:52:40 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
fix(router): correct over-encoding of URL fragment (#22687)
2018-03-11 22:15:01 -07:00
test
fix(router): correct over-encoding of URL fragment (#22687)
2018-03-11 22:15:01 -07:00
testing
feat(bazel): change ng_package rule to APF v6 (#22782)
2018-03-15 11:38:31 -07:00
upgrade
feat: mark angular packages as side-effect free (#22785)
2018-03-15 14:52:40 -07:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
feat(bazel): change ng_package rule to APF v6 (#22782)
2018-03-15 11:38:31 -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
build: add bazel test rules for remainder of packages (#21053)
2017-12-22 13:10:51 -08:00
karma.conf.js
build: build modules and examples for karma
2017-03-08 17:35:20 -08:00
LICENSE
docs(common): update copyright years (#21232)
2018-01-04 17:45:36 -05:00
package.json
feat: mark angular packages as side-effect free (#22785)
2018-03-15 14:52:40 -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
fix: add missing globals from each rollup configuration (#20028)
2017-10-30 23:09:17 -04: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