`loadComponent` is the route-level option for lazy-loading a standalone component. Put the route in the root route table (or a lazy feature route) and use a dynamic import: ```ts // src/app/app.routes.ts import { Routes } from '@angular/router'; export const routes: Routes = [ { path: 'dashboard', loadComponent: () => import('./features/dashboard/dashboard.component').then( (m) => m.DashboardComponent, ), }, ]; ``` The target component must be standalone: ```ts @Component({ selector: 'app-das...
Scanned 9/5/2026
Install to Claude Code
npx -y skills add HoangNguyen0403/agent-skills-standard --skill angular-architecture --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Angular Architecture?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-angular-architecture-d1cc3c5f)More formats (shields.io, HTML) on the badges page.
# Configuring lazy loading with `loadComponent`
`loadComponent` is the route-level option for lazy-loading a standalone component. Put the route in the root route table (or a lazy feature route) and use a dynamic import:
```ts
// src/app/app.routes.ts
import { Routes } from '@angular/router';
export const routes: Routes = [
{
path: 'dashboard',
loadComponent: () =>
import('./features/dashboard/dashboard.component').then(
(m) => m.DashboardComponent,
),
},
];
```
The target component must be standalone:
```ts
@Component({
selector: 'app-dashboard',
standalone: true,
imports: [DashboardSummaryComponent],
template: `<app-dashboard-summary />`,
})
export class DashboardComponent {}
```
Do not add a top-level eager import of `DashboardComponent`; the dynamic import is what creates the lazy boundary. Declare the component's template dependencies in its own `imports` array. Use `loadChildren` when the feature has a group of child routes, and use `loadComponent` for a standalone leaf page or route entry.
Verify the route path, exported component name, and import path, then confirm every feature route uses `loadComponent` or `loadChildren`. Keep the page under a feature folder, keep application-wide services in `core/`, and avoid introducing an NgModule just to support this route.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!