mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
2d713f5847
This change separates the router initializer into different providers. While it does not actually change the tree-shakeablity or the public API, it does move us towards a world that _could_ do this. That is, instead of `initialNavigation: 'disabled'`, users could use `provideDisabledInitialNavigation` in the `bootstrapApplication` call and none of the code for `initialNavigation: 'enabledBlocking'` would be included in the application. PR Close #46215
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.