Angular project structure walkthrough

Introduction

An Angular project has many files and folders. Understanding the structure helps you find and change code easily.

When you start a new Angular project and want to know where to put your code.

When you join a team and need to understand how the project is organized.

When you want to add new features or fix bugs and need to find the right files.

When you want to keep your project clean and easy to maintain.

When you want to learn Angular by exploring a real project.

Syntax

Angular

angular-project/
├── e2e/
├── node_modules/
├── src/
│   ├── app/
│   │   ├── components/
│   │   ├── services/
│   │   ├── app.component.ts
│   │   ├── app.module.ts
│   ├── assets/
│   ├── environments/
│   ├── index.html
│   ├── main.ts
│   ├── styles.css
├── angular.json
├── package.json
├── tsconfig.json

The src/ folder contains your app code and assets.

Configuration files like angular.json and package.json control the project setup and dependencies.

Examples

This file holds the main component code that controls the app's main view.

Angular

src/app/app.component.ts

This file declares and organizes components and services in the app.

Angular

src/app/app.module.ts

This folder stores images, icons, and other static files used in the app.

Angular

src/assets/

This file configures how Angular builds and serves your project.

Angular

angular.json

Sample Program

This shows the core files in an Angular project: a main component, a module to organize it, and the main entry file to start the app.

Angular

/* This is a simple Angular project structure overview */

// src/app/app.component.ts
import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  template: `<h1>Welcome to Angular!</h1>`,
  styles: [`h1 { color: darkblue; }`]
})
export class AppComponent {}

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

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

// src/main.ts
import { platformBrowserDynamic } from '@angular/platform-browser-dynamic';
import { AppModule } from './app/app.module';

platformBrowserDynamic().bootstrapModule(AppModule)
  .catch(err => console.error(err));

Important Notes

Folders like e2e/ are for testing your app automatically.

Keep your components and services organized in separate folders inside src/app/.

Use angular.json to customize build and development settings.

Summary

An Angular project has a clear folder structure to keep code organized.

The src/ folder holds your app code, assets, and styles.

Key files like app.component.ts and app.module.ts define your app's building blocks.

Practice

1. Which folder in an Angular project typically contains the main application code and assets?

easy

A. src/

B. node_modules/

C. dist/

D. e2e/

Solution

1. Step 1: Understand Angular folder roles

   The src/ folder holds the source code including app files and assets.

2. Step 2: Identify other folders' purposes

   node_modules/ holds external libraries, dist/ is for build output, and e2e/ is for end-to-end tests.

3. Final Answer:

   src/ -> Option A

4. Quick Check:

   App code and assets = src/ [OK]

Hint: Remember: src means source code folder [OK]

Common Mistakes:

• Confusing node_modules with source code
• Thinking dist holds source files
• Assuming e2e contains app code

2. Which file defines the root component of an Angular application?

easy

A. app.module.ts

B. app.component.ts

C. main.ts

D. index.html

Solution

1. Step 1: Identify root component file

   The root component is defined in app.component.ts, which contains the main UI logic.

2. Step 2: Differentiate other files

   app.module.ts defines the app module, main.ts bootstraps the app, and index.html is the main HTML page.

3. Final Answer:

   app.component.ts -> Option B

4. Quick Check:

   Root component = app.component.ts [OK]

Hint: Component files end with .component.ts [OK]

Common Mistakes:

• Confusing app.module.ts with component file
• Thinking main.ts defines UI
• Assuming index.html is a component

3. Given this Angular project structure snippet:

src/
  app/
    app.module.ts
    app.component.ts
  assets/
  styles.css

Which file is responsible for declaring components and importing modules?

medium

A. assets/

B. styles.css

C. app.component.ts

D. app.module.ts

Solution

1. Step 1: Understand app.module.ts role

   This file declares components and imports other Angular modules to organize the app.

2. Step 2: Clarify other files' roles

   app.component.ts defines UI logic, styles.css holds styles, and assets/ stores static files.

3. Final Answer:

   app.module.ts -> Option D

4. Quick Check:

   Module declarations = app.module.ts [OK]

Hint: Modules declare components, components define UI [OK]

Common Mistakes:

• Mixing component and module responsibilities
• Thinking styles.css declares components
• Confusing assets folder with code files

4. You see this error when running an Angular app:
ERROR in src/app/app.module.ts: Unexpected token
What is the most likely cause in the app.module.ts file?

medium

A. Missing @NgModule decorator

B. Empty app.component.ts file

C. Syntax error like missing comma or bracket

D. Wrong file extension instead of .ts

Solution

1. Step 1: Analyze error message

   An "Unexpected token" error usually means a syntax mistake like a missing comma or bracket.

2. Step 2: Check common syntax issues in app.module.ts

   Look for missing commas, brackets, or typos in imports or declarations.

3. Final Answer:

   Syntax error like missing comma or bracket -> Option C

4. Quick Check:

   Unexpected token = syntax error [OK]

Hint: Unexpected token means syntax mistake [OK]

Common Mistakes:

• Assuming missing decorator causes token error
• Blaming wrong file extension without checking syntax
• Thinking empty component file causes this error

5. You want to add a new feature module to your Angular app. Where should you place the new module file and what must you do to use it in your app?

hard

A. Place it inside src/app/ and import it in app.module.ts

B. Place it in src/assets/ and reference it in index.html

C. Place it in src/ root and add it to main.ts

D. Place it in src/styles/ and import in styles.css

Solution

1. Step 1: Locate new module in project structure

   Feature modules go inside src/app/ to keep app code organized.

2. Step 2: Import new module in app.module.ts

   To use the new module, import it in app.module.ts so Angular knows about it.

3. Final Answer:

   Place it inside src/app/ and import it in app.module.ts -> Option A

4. Quick Check:

   Feature module location and import = Place it inside src/app/ and import it in app.module.ts [OK]

Hint: Modules live in src/app and must be imported [OK]

Common Mistakes:

• Putting modules in assets or styles folders
• Forgetting to import the module in app.module.ts
• Adding modules to main.ts or index.html incorrectly