angular/packages/router
Andrew Scott c45c5205b5 refactor(router): Update afterRender phase to use old API (#56526)
The new API does not exist in the 18 branch

PR Close #56526
2024-06-20 10:43:33 -07:00
..
scripts refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
src refactor(router): Update afterRender phase to use old API (#56526) 2024-06-20 10:43:33 -07:00
test fix(router): Scroller should scroll as soon as change detection completes (#55105) 2024-04-30 09:19:14 -07:00
testing docs(router): deprecate RouterTestingModule (#54466) 2024-02-20 09:33:16 -08:00
upgrade refactor: migrate router to prettier formatting (#54318) 2024-02-08 19:17:14 +00:00
.gitignore refactor: move angular source to /packages rather than modules/@angular 2017-03-08 16:29:27 -08:00
BUILD.bazel refactor(docs-infra): complete removal of aio directory (#56496) 2024-06-18 12:26:04 -07:00
index.ts build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
package.json build: update Node.js to match Angular CLI engines (#56187) 2024-06-03 18:00:46 +00:00
PACKAGE.md docs: Use new Urls to drop the docs url mapper (#55043) 2024-04-09 12:23:09 -07:00
public_api.ts build: update license headers to reference Google LLC (#37205) 2020-05-26 14:26:58 -04:00
README.md docs: Use new Urls to drop the docs url mapper (#55043) 2024-04-09 12:23:09 -07:00

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 isnt 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.