Router for Angulars
The Angular router maps URLs to components so a single-page app can have multiple views. It handles route configuration, parameters, nested routes, guards, resolvers and lazy loading. Alongside it, state management decides where shared data lives, using services with signals or a store library.
Stage: Application Structure · Part of the Angular roadmap · Last reviewed 19 November 2026
What to learn in Router
- Configure routes with paths, parameters and child routes
- Protect a route with a functional canActivate guard
- Lazy load a feature using loadComponent or loadChildren
- Read route parameters and query parameters inside a component
- Share state across routes with a service built on signals
Router interview questions
What is lazy loading in the Angular router?
Lazy loading splits the code for a route into a separate bundle that downloads only when the user first navigates there. Using loadComponent or loadChildren shrinks the initial bundle and speeds up the first page, at the cost of a small delay on first visit.
What is the difference between a guard and a resolver?
A guard decides whether navigation may proceed, for example blocking an unauthenticated user, by returning true, false or a redirect. A resolver fetches data before the route activates so the component already has it. One controls access, the other prepares data.
Where Router fits in the Angular roadmap
Router belongs to the Application Structure stage (intermediate level), which takes about 24 hours. Routing and forms.
Other units in this stage
Back to the full Angular roadmap