Lazy loading modules with routes in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is lazy loading in Angular routing?

Lazy loading is a technique where Angular loads feature modules only when the user navigates to their routes, reducing the initial load time of the app.

beginner

How do you define a lazy loaded module in Angular routes?

You use the <code>loadChildren</code> property in the route configuration to specify the module path and class name, like <code>{ path: 'feature', loadChildren: () =&gt; import('./feature/feature.module').then(m =&gt; m.FeatureModule) }</code>.

beginner

Why is lazy loading beneficial for Angular apps?

It improves app startup speed by loading only the necessary code first, and loads other parts only when needed, saving bandwidth and improving user experience.

intermediate

What must a lazy loaded Angular module include to work correctly with routing?

It must have its own RouterModule.forChild() with routes defined, so Angular knows how to handle navigation inside that module.

intermediate

Can lazy loaded modules share services with the root module?

Yes, if services are provided in the root injector (using providedIn: 'root'), lazy loaded modules can share them. Otherwise, services provided inside lazy modules are scoped to that module only.

Which property is used to lazy load a module in Angular routes?

A component

B pathMatch

C children

D loadChildren

The loadChildren property tells Angular to load a module lazily when its route is accessed.

What method should a lazy loaded module use to define its routes?

A RouterModule.forChild()

B RouterModule.lazyLoad()

C RouterModule.forRoot()

D RouterModule.loadModule()

Lazy loaded modules use RouterModule.forChild() to define their internal routes.

What is a key benefit of lazy loading modules in Angular?

A Faster initial app load

B More complex code

C Larger bundle size

D Slower navigation

Lazy loading reduces the initial bundle size, making the app load faster at start.

How do you specify the module to load lazily in Angular routing?

A Using a component reference

B Using a string path only

C Using a function that imports the module

D Using a service

You provide a function that returns a dynamic import promise for the module.

If a service is provided inside a lazy loaded module, what is its scope?

A Global app scope

B Only inside that lazy loaded module

C Available in all modules automatically

D Only in root module

Services provided inside a lazy loaded module are scoped to that module only unless provided in root.

Explain how lazy loading modules with routes works in Angular and why it is useful.

Think about how Angular loads parts of the app only when you visit their pages.

Describe the steps to set up a lazy loaded feature module with routing in Angular.

Focus on module creation, routing inside it, and main app routing configuration.

Practice

1. What is the main purpose of lazy loading modules in Angular routing?

easy

A. To preload all modules when the app starts

B. To load modules only when the user navigates to their route

C. To load modules in alphabetical order

D. To load all modules at once for faster navigation

Solution

1. Step 1: Understand lazy loading concept

   Lazy loading means delaying the loading of a module until it is needed, usually when the user navigates to a route that requires it.

2. Step 2: Identify the purpose in routing

   In Angular routing, lazy loading helps improve app speed by loading modules only on demand, not all at once.

3. Final Answer:

   To load modules only when the user navigates to their route -> Option B

4. Quick Check:

   Lazy loading = load on demand [OK]

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

Common Mistakes:

• Thinking lazy loading loads all modules at start
• Confusing lazy loading with preloading
• Assuming lazy loading loads modules alphabetically

2. Which of the following is the correct syntax to lazy load a module named AdminModule in Angular routes?

easy

A. { path: 'admin', loadChildren: import('./admin/admin.module') }

B. { path: 'admin', loadChildren: './admin/admin.module#AdminModule' }

C. { path: 'admin', component: AdminModule }

D. { path: 'admin', loadChildren: () => import('./admin/admin.module').then(m => m.AdminModule) }

Solution

1. Step 1: Recall Angular lazy loading syntax

   Angular uses dynamic import with a function returning a promise that resolves to the module class.

2. Step 2: Match syntax to options

   { path: 'admin', loadChildren: () => import('./admin/admin.module').then(m => m.AdminModule) } uses the correct arrow function with import and then to get AdminModule. { path: 'admin', loadChildren: './admin/admin.module#AdminModule' } is old deprecated string syntax. Options C and D are incorrect usage.

3. Final Answer:

   { path: 'admin', loadChildren: () => import('./admin/admin.module').then(m => m.AdminModule) } -> Option D

4. Quick Check:

   Dynamic import with arrow function = correct syntax [OK]

Hint: Use arrow function with import().then() for lazy loading [OK]

Common Mistakes:

• Using deprecated string syntax for loadChildren
• Assigning component instead of loadChildren
• Omitting the arrow function wrapper

3. Given this route configuration snippet:

{ path: 'shop', loadChildren: () => import('./shop/shop.module').then(m => m.ShopModule) }

What happens when the user navigates to /shop for the first time?

medium

A. The ShopModule is already loaded at app start, so navigation is instant

B. Navigation fails because loadChildren requires a component

C. The ShopModule is loaded asynchronously and its routes are activated

D. The entire app reloads to load ShopModule

Solution

1. Step 1: Understand lazy loading behavior on navigation

   When navigating to a lazy loaded route for the first time, Angular loads the module asynchronously.

2. Step 2: Identify what happens on first navigation

   The ShopModule is fetched, loaded, and its routes become active, enabling the user to see the shop page.

3. Final Answer:

   The ShopModule is loaded asynchronously and its routes are activated -> Option C

4. Quick Check:

   First navigation triggers async module load [OK]

Hint: First visit loads module asynchronously, not at app start [OK]

Common Mistakes:

• Assuming module loads at app start
• Confusing loadChildren with component property
• Thinking app reloads on lazy load

4. Identify the error in this Angular route configuration for lazy loading:

{ path: 'dashboard', loadChildren: './dashboard/dashboard.module#DashboardModule' }

medium

A. Using string syntax for loadChildren is deprecated and causes errors

B. Missing component property for the route

C. Path should be capitalized as 'Dashboard'

D. loadChildren should be a component, not a string

Solution

1. Step 1: Check loadChildren syntax

   The string syntax with '#ModuleName' is deprecated in Angular and may cause errors in recent versions.

2. Step 2: Identify correct syntax

   Modern Angular requires loadChildren to be a function returning a dynamic import promise, not a string.

3. Final Answer:

   Using string syntax for loadChildren is deprecated and causes errors -> Option A

4. Quick Check:

   Use dynamic import function, not string [OK]

Hint: Avoid string syntax; use dynamic import function [OK]

Common Mistakes:

• Using old string syntax for loadChildren
• Confusing component and loadChildren properties
• Ignoring case sensitivity in paths

5. You want to lazy load a feature module ProfileModule only when the user navigates to /profile. The module has child routes. Which is the best way to configure the main app routing to achieve this and ensure accessibility and performance?

hard

A. { path: 'profile', loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule), canActivate: [AuthGuard] }

B. { path: 'profile', component: ProfileModule }

C. { path: 'profile', loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule) }

D. { path: 'profile', loadChildren: './profile/profile.module#ProfileModule' }

Solution

1. Step 1: Identify modern lazy loading syntax

   The correct syntax uses dynamic import with an arrow function returning a promise: loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule).

2. Step 2: Consider best practices for accessibility and performance

   For protected features like a user profile, adding canActivate: [AuthGuard] ensures secure access while lazy loading maintains performance.

3. Step 3: Eliminate incorrect configurations

   Using component property fails for modules with child routes. String syntax like './profile/profile.module#ProfileModule' is deprecated.

4. Final Answer:

   { path: 'profile', loadChildren: () => import('./profile/profile.module').then(m => m.ProfileModule), canActivate: [AuthGuard] } -> Option A

5. Quick Check:

   Lazy load with guard for best practice [OK]

Hint: Lazy load with import and add guards for security [OK]

Common Mistakes:

• Using component instead of loadChildren for modules
• Using deprecated string syntax
• Forgetting route guards for protected routes