Feature modules for organization in Angular - Mini Project: Build & Apply

Feature modules for organization

📖 Scenario: You are building a simple Angular app that shows a list of books and authors. To keep your code clean and organized, you want to separate the book-related code into its own feature module.

🎯 Goal: Create a feature module called BooksModule that declares a BooksComponent. Then import this module into the main AppModule so the app can display the books list.

📋 What You'll Learn

Create a feature module named BooksModule

Declare a component named BooksComponent inside BooksModule

Add a simple template in BooksComponent that shows the text 'Books list here'

Import BooksModule into the main AppModule

Bootstrap the AppComponent in AppModule

💡 Why This Matters

🌍 Real World

Feature modules help keep Angular apps organized by grouping related code. This makes apps easier to maintain and scale.

💼 Career

Understanding feature modules is essential for Angular developers working on medium to large projects where code organization is critical.

1

Create the BooksComponent

Create a component named BooksComponent with a selector app-books and a template that contains the text Books list here. Use the @Component decorator and export the class.

Angular

// Your code here to create BooksComponent

Hint

Use @Component decorator with selector and template properties. Export the class BooksComponent.

2

Create the BooksModule

Create a feature module named BooksModule using the @NgModule decorator. Declare the BooksComponent inside the declarations array. Export the BooksComponent in the exports array.

Angular

import { Component } from '@angular/core';
import { NgModule } from '@angular/core';

@Component({
  selector: 'app-books',
  template: 'Books list here'
})
export class BooksComponent {}

// Your code here to create BooksModule

Hint

Use @NgModule decorator with declarations and exports arrays. Export the class BooksModule.

3

Create the AppComponent

Create a root component named AppComponent with selector app-root. Its template should include the app-books selector to display the books list.

Angular

import { Component } from '@angular/core';
import { NgModule } from '@angular/core';

@Component({
  selector: 'app-books',
  template: 'Books list here'
})
export class BooksComponent {}

@Component({
  selector: 'app-root',
  template: ''
})
export class AppComponent {}

// Your code here to create AppComponent

Hint

Use @Component decorator with selector and template. Export AppComponent.

4

Create the AppModule and import BooksModule

Create the root module named AppModule using @NgModule. Declare AppComponent in declarations. Import BooksModule in imports. Bootstrap the AppComponent.

Angular

import { Component } from '@angular/core';
import { NgModule } from '@angular/core';

@Component({
  selector: 'app-books',
  template: 'Books list here'
})
export class BooksComponent {}

@NgModule({
  declarations: [BooksComponent],
  exports: [BooksComponent]
})
export class BooksModule {}

@Component({
  selector: 'app-root',
  template: ''
})
export class AppComponent {}

// Your code here to create AppModule and import BooksModule

Hint

Use @NgModule with declarations, imports, and bootstrap. Import BrowserModule and BooksModule. Export AppModule.

Practice

1. What is the main purpose of a feature module in Angular?

easy

A. To store global styles for the app

B. To replace the root AppModule entirely

C. To group related components, directives, and services for better organization

D. To handle routing only

Solution

1. Step 1: Understand feature module role

   Feature modules group related parts like components and services to keep code organized.

2. Step 2: Compare other options

   Feature modules do not replace AppModule, are not only for routing, and do not store styles.

3. Final Answer:

   To group related components, directives, and services for better organization -> Option C

4. Quick Check:

   Feature modules organize related code = D [OK]

Hint: Feature modules group related code parts [OK]

Common Mistakes:

• Thinking feature modules replace AppModule
• Believing feature modules only handle routing
• Confusing feature modules with style storage

2. Which of the following is the correct way to import a feature module named ProductsModule into the root module?

easy

A. declarations: [ProductsModule]

B. imports: [ProductsModule]

C. providers: [ProductsModule]

D. bootstrap: [ProductsModule]

Solution

1. Step 1: Recall Angular module metadata

   Feature modules are imported using the imports array in @NgModule.

2. Step 2: Understand other arrays

   declarations is for components/directives, providers for services, bootstrap for root component.

3. Final Answer:

   imports: [ProductsModule] -> Option B

4. Quick Check:

   Feature modules go in imports = B [OK]

Hint: Import feature modules inside imports array [OK]

Common Mistakes:

• Putting modules in declarations array
• Adding modules to providers array
• Using bootstrap array for modules

3. Given this code snippet in app.module.ts:

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { ProductsModule } from './products/products.module';
import { AppComponent } from './app.component';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule, ProductsModule],
  bootstrap: [AppComponent]
})
export class AppModule { }

What will happen if ProductsModule declares and exports a component ProductListComponent and you use <app-product-list> in AppComponent template?

medium

A. The ProductListComponent will render correctly inside AppComponent

B. Angular will throw a template parse error because ProductListComponent is not declared in AppModule

C. The app will compile but ProductListComponent will not display anything

D. The app will crash at runtime with a component not found error

Solution

1. Step 1: Understand module imports and declarations

   Since ProductsModule is imported in AppModule, its declared components are available in AppModule's templates.

2. Step 2: Check component usage in template

   Using <app-product-list> in AppComponent works because ProductListComponent is exported by ProductsModule.

3. Final Answer:

   The ProductListComponent will render correctly inside AppComponent -> Option A

4. Quick Check:

   Imported module components usable in templates = A [OK]

Hint: Imported module components can be used in root templates [OK]

Common Mistakes:

• Thinking components must be declared in AppModule to use
• Assuming runtime crash instead of compile error
• Believing imported components won't render

4. You have a feature module OrdersModule but when you try to use its component OrderListComponent in AppComponent, Angular shows an error: 'app-order-list' is not a known element. What is the most likely cause?

medium

A. OrdersModule was not imported into AppModule

B. OrderListComponent was not declared in OrdersModule

C. OrdersModule was added to declarations instead of imports

D. OrderListComponent selector is misspelled in the template

Solution

1. Step 1: Check module import

   If OrdersModule is not imported in AppModule, its components are unknown in root templates.

2. Step 2: Review other options

   While declaration or selector errors cause issues, the common cause for 'not a known element' is missing module import.

3. Final Answer:

   OrdersModule was not imported into AppModule -> Option A

4. Quick Check:

   Missing module import causes unknown element error = C [OK]

Hint: Always import feature modules in AppModule to use their components [OK]

Common Mistakes:

• Forgetting to import the feature module
• Adding module to declarations array
• Ignoring selector typos

5. You want to organize your Angular app by creating two feature modules: UsersModule and AdminModule. AdminModule needs to use components from UsersModule. How should you set up the modules to allow this?

hard

A. Use providers array to share components between modules

B. Import AdminModule into UsersModule and export needed components from AdminModule

C. Declare all components in both modules to share them

D. Import UsersModule into AdminModule and export needed components from UsersModule

Solution

1. Step 1: Understand module dependency direction

   If AdminModule needs UsersModule components, UsersModule must be imported into AdminModule.

2. Step 2: Export components from UsersModule

   Only exported components from UsersModule are visible to AdminModule.

3. Final Answer:

   Import UsersModule into AdminModule and export needed components from UsersModule -> Option D

4. Quick Check:

   Import dependency module and export components = A [OK]

Hint: Import and export modules to share components [OK]

Common Mistakes:

• Importing modules in wrong direction
• Declaring components in multiple modules
• Using providers to share components