Lazy loading standalone components in Angular - Step-by-Step Execution

Concept Flow - Lazy loading standalone components

User navigates to route

↓

Check if component is loaded

↓

Load component asynchronously

↓

Initialize standalone component

↓

Render component in view

↓

User interacts with component

When a user navigates to a route, Angular checks if the standalone component is loaded. If not, it loads it asynchronously, initializes it, and renders it.

Execution Sample

Angular

const routes = [
  { path: 'profile', loadComponent: () => import('./profile.component').then(m => m.ProfileComponent) }
];

Defines a route that lazy loads a standalone component when the user navigates to '/profile'.

Execution Table

Step	Action	Condition	Result	Component State
1	User navigates to '/profile'	Component loaded? No	Start loading component asynchronously	Not loaded
2	Import profile.component module	Module loaded? No	Fetch module file	Loading
3	Module fetched	Module loaded? Yes	Resolve ProfileComponent	Loaded
4	Initialize ProfileComponent	Component initialized? No	Create component instance	Initialized
5	Render ProfileComponent	Component rendered? No	Insert component into view	Rendered
6	User interacts with component	Component active? Yes	Handle user events	Active
7	User navigates away	Unload component? Yes	Destroy component instance	Not loaded

💡 Component is unloaded when user navigates away or app is closed.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	Final
componentLoaded	false	false	true	true	false
componentInstance	null	null	instance created	instance active	null
componentRendered	false	false	false	true	false

Key Moments - 3 Insights

Why does Angular load the component only after navigation?

Because the route uses loadComponent with a dynamic import, Angular waits until the user navigates to that route before fetching and initializing the component, as shown in execution_table step 1 and 2.

What happens if the component is already loaded and user navigates again?

Angular reuses the loaded component without fetching again, skipping the loading steps. This is implied by the 'Component loaded? Yes' condition in step 3.

How does Angular know when to destroy the component?

When the user navigates away, Angular destroys the component instance to free resources, as shown in step 7 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the component instance created?

A Step 4

B Step 2

C Step 5

D Step 3

💡 Hint

Check the 'Action' and 'Result' columns around component initialization.

At which step does Angular insert the component into the view?

A Step 6

B Step 3

C Step 5

D Step 4

💡 Hint

Look for the step mentioning 'Render ProfileComponent' in the Action column.

If the user navigates away immediately after rendering, what happens to componentLoaded variable?

A Remains true

B Changes to false

C Becomes null

D Does not change

💡 Hint

Refer to variable_tracker and execution_table step 7 about unloading the component.

Concept Snapshot

Lazy loading standalone components in Angular:
- Use loadComponent with dynamic import in route config
- Component loads only on navigation to route
- Angular fetches module, initializes, and renders component
- Component destroyed on navigation away
- Improves app startup speed by loading on demand

Full Transcript

Lazy loading standalone components in Angular means the app waits to load a component until the user navigates to its route. The route uses loadComponent with a dynamic import function. When navigation happens, Angular checks if the component is loaded. If not, it fetches the module file asynchronously, creates the component instance, and renders it in the view. The component stays active while the user interacts. When the user leaves the route, Angular destroys the component to save resources. This process helps apps start faster by loading only what is needed when needed.

Practice

1. What is the main benefit of lazy loading standalone components in Angular?

easy

A. It bundles all components into a single file

B. It automatically updates components without user action

C. It disables component rendering on mobile devices

D. It improves app speed by loading components only when needed

Solution

1. Step 1: Understand lazy loading purpose

   Lazy loading delays loading parts of the app until they are needed, reducing initial load time.

2. Step 2: Connect lazy loading to standalone components

   Standalone components can be lazy loaded to improve app speed by not loading them upfront.

3. Final Answer:

   It improves app speed by loading components only when needed -> Option D

4. Quick Check:

   Lazy loading = improves speed [OK]

Hint: Lazy loading means load only when needed [OK]

Common Mistakes:

• Thinking lazy loading bundles all components together
• Confusing lazy loading with automatic updates
• Believing lazy loading disables components on devices

2. Which syntax correctly lazy loads a standalone component in Angular routing?

easy

A. { path: 'home', loadComponent: () => import('./home.component').then(m => m.HomeComponent) }

B. { path: 'home', component: () => import('./home.component').then(m => m.HomeComponent) }

C. { path: 'home', loadChildren: () => import('./home.component').then(m => m.HomeComponent) }

D. { path: 'home', loadModule: () => import('./home.component').then(m => m.HomeComponent) }

Solution

1. Step 1: Identify correct property for lazy loading standalone components

   Angular uses loadComponent to lazy load standalone components in routes.

2. Step 2: Check syntax correctness

   { path: 'home', loadComponent: () => import('./home.component').then(m => m.HomeComponent) } uses loadComponent with dynamic import and then returns the component class, which is correct.

3. Final Answer:

   { path: 'home', loadComponent: () => import('./home.component').then(m => m.HomeComponent) } -> Option A

4. Quick Check:

   Lazy load standalone = loadComponent [OK]

Hint: Use loadComponent with dynamic import for standalone lazy loading [OK]

Common Mistakes:

• Using component property instead of loadComponent
• Using loadChildren for components instead of modules
• Using non-existent loadModule property

3. Given this route config, what happens when navigating to '/dashboard'?

{ path: 'dashboard', loadComponent: () => import('./dashboard.component').then(m => m.DashboardComponent) }

medium

A. The DashboardComponent is loaded immediately when the app starts

B. The DashboardComponent is loaded only when '/dashboard' is visited

C. The DashboardComponent is never loaded

D. The app throws a runtime error due to missing component

Solution

1. Step 1: Understand loadComponent behavior

   Using loadComponent with dynamic import delays loading the component until the route is accessed.

2. Step 2: Apply to '/dashboard' route

   The DashboardComponent will load only when the user navigates to '/dashboard', not before.

3. Final Answer:

   The DashboardComponent is loaded only when '/dashboard' is visited -> Option B

4. Quick Check:

   loadComponent = lazy load on route visit [OK]

Hint: loadComponent loads component on route visit only [OK]

Common Mistakes:

• Assuming component loads at app start
• Thinking component never loads
• Expecting runtime error without import

4. Identify the error in this route config for lazy loading a standalone component:

{ path: 'profile', loadComponent: import('./profile.component').then(m => m.ProfileComponent) }

medium

A. Missing arrow function wrapping the import call

B. Using loadComponent instead of component property

C. Incorrect path string format

D. Missing import statement at the top of the file

Solution

1. Step 1: Check loadComponent syntax

   The loadComponent property must be a function returning a Promise, so it needs an arrow function wrapping the import.

2. Step 2: Identify missing arrow function

   The code calls import directly without wrapping in a function, causing the component to load eagerly or a runtime error when the router tries to invoke it.

3. Final Answer:

   Missing arrow function wrapping the import call -> Option A

4. Quick Check:

   loadComponent requires () => import(...) [OK]

Hint: Wrap import in arrow function for loadComponent [OK]

Common Mistakes:

• Calling import directly without function
• Confusing loadComponent with component property
• Thinking import must be at file top

5. You want to lazy load two standalone components, AdminComponent and UserComponent, under routes '/admin' and '/user'. Which is the best way to configure the routes to optimize initial load time?

hard

A. Import both components eagerly and assign them to routes directly

B. Use loadChildren to lazy load a module containing both components

C. Use loadComponent with dynamic imports for both routes separately

D. Combine both components into one and lazy load that single component

Solution

1. Step 1: Understand lazy loading standalone components

   Using loadComponent with dynamic imports allows each component to load only when its route is visited, reducing initial load.

2. Step 2: Compare options for multiple components

   Use loadComponent with dynamic imports for both routes separately loads each component lazily and separately, optimizing load time better than eager loading or bundling.

3. Final Answer:

   Use loadComponent with dynamic imports for both routes separately -> Option C

4. Quick Check:

   Separate loadComponent calls = best lazy loading [OK]

Hint: Lazy load each standalone component separately with loadComponent [OK]

Common Mistakes:

• Eagerly importing components defeats lazy loading
• Using loadChildren for standalone components unnecessarily
• Combining components increases initial load size