honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/packages/router
History
Alan Agius 772c5b8f64 refactor: update to tslib 2.0 and move to direct dependencies (#37198) 
Tslib version is bound to the TypeScript version used to compile the library. Thus, we shouldn't list `tslib` as a  `peerDependencies`. This is because, a user can install libraries which have been compiled with older versions of TypeScript and thus require multiple `tslib` versions to be installed.

Reference: TOOL-1374 and TOOL-1375

Closes: #37188

PR Close #37198
2020-05-19 14:57:09 -07:00
..
scripts
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
src
docs(router): corrected minor typo (#37166)
2020-05-18 16:23:31 -07:00
test
fix(router): update type for routerLink to include null and undefined (#37018)
2020-05-18 14:55:41 -07:00
testing
build: simplify package.jsons for all of our packages (#36944)
2020-05-06 13:54:26 -07:00
upgrade
build: simplify package.jsons for all of our packages (#36944)
2020-05-06 13:54:26 -07:00
.gitignore
refactor: move angular source to /packages rather than modules/@angular
2017-03-08 16:29:27 -08:00
BUILD.bazel
build: provide full paths to ts_api_guardian_test_npm_package and ts_api_guardian_test (#36034)
2020-03-12 09:49:00 -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: reformat repo to new clang@1.4.0 (#36613)
2020-04-14 12:08:36 -07:00
karma.conf.js
build: reference zone.js from source directly instead of npm. (#33046)
2019-11-06 00:48:34 +00:00
package.json
refactor: update to tslib 2.0 and move to direct dependencies (#37198)
2020-05-19 14:57:09 -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

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.