honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Paul Gschwendtner 7cbc36fdac build: remove unused rollup.config.js files (#28646) 
Since we build and publish the individual packages
using Bazel and `build.sh` has been removed, we can
safely remove the `rollup.config.js` files which are no
longer needed because the `ng_package` bazel rule
automatically handles the rollup settings and globals.

PR Close #28646
2019-02-14 19:28:08 +00:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
refactor(router): change RouterLinkActive impl to account for upcoming ivy breaking change (#28560)
2019-02-08 16:42:45 -08:00
test
refactor(router): change RouterLinkActive impl to account for upcoming ivy breaking change (#28560)
2019-02-08 16:42:45 -08:00
testing
build: remove unused rollup.config.js files (#28646)
2019-02-14 19:28:08 +00:00
upgrade
build: remove unused rollup.config.js files (#28646)
2019-02-14 19:28:08 +00:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
build: run offline_compiler_test using bazel (#28191)
2019-01-28 20:07:22 -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(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
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
docs(router): remove obsolete sections in README.md (#27880)
2019-01-11 11:15:59 -08: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.

Guide

Read the dev guide here.