mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
JoostK
361273fad5
This commit removes the ability to configure lazy routes using a string for `loadChildren`, together with the supporting classes to load an `NgModuleFactory` at runtime. BREAKING CHANGE: It is no longer possible to use `Route.loadChildren` using a string value. The following supporting classes were removed from `@angular/core`: - `NgModuleFactoryLoader` - `SystemJsNgModuleFactoryLoader` The `@angular/router` package no longer exports these symbols: - `SpyNgModuleFactoryLoader` - `DeprecatedLoadChildren` The signature of the `setupTestingRouter` function from `@angular/core/testing` has been changed to drop its `NgModuleFactoryLoader` parameter, as an argument for that parameter can no longer be created. PR Close #43591
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.