Why TypeScript is required in Angular - See It in Action

Why TypeScript is required in Angular

📖 Scenario: You are building a simple Angular app to display a list of users. You want to understand why Angular uses TypeScript instead of plain JavaScript.

🎯 Goal: Learn how to set up a basic Angular component using TypeScript and see how TypeScript helps with type safety and better code structure.

📋 What You'll Learn

Create a user list array with exact user names

Add a TypeScript type for the user data

Use Angular standalone component with TypeScript

Display the user list in the template

💡 Why This Matters

🌍 Real World

Most Angular apps use TypeScript to build reliable and maintainable web applications with clear code structure.

💼 Career

Understanding why Angular uses TypeScript is essential for frontend developers working with Angular frameworks in professional environments.

1

Create a user list array

Create a constant array called users with these exact string values: 'Alice', 'Bob', 'Charlie'.

Angular

# Create a constant array called users with 'Alice', 'Bob', 'Charlie'
# Your code here

Hint

Use const users = ['Alice', 'Bob', 'Charlie']; to create the array.

2

Add a TypeScript type for users

Create a TypeScript type alias called User as string. Then create a constant array called users with type User[] and the same values: 'Alice', 'Bob', 'Charlie'.

Angular

type User = string;
const users: User[] = ['Alice', 'Bob', 'Charlie'];
# Your code here

Hint

Use type User = string; and const users: User[] = [...].

3

Create an Angular standalone component

Create a standalone Angular component called UserListComponent using @Component decorator. Use selector: 'app-user-list', and add a template that uses *ngFor="let user of users" to display each user inside a <li>. Import CommonModule and declare users as a public property with type User[] initialized to the users array.

Angular

import { Component } from '@angular/core';
import { CommonModule } from '@angular/common';

@Component({
  selector: 'app-user-list',
  standalone: true,
  imports: [CommonModule],
  template: `
    
      {{ user }}
    
  `
})
export class UserListComponent {
  users: User[] = users;
}
# Your code here

Hint

Use @Component with standalone: true and import CommonModule. Use *ngFor in template.

4

Complete the component setup

Export the UserListComponent class and ensure it uses the users array typed as User[]. Confirm the template displays the list of users with <li> elements inside a <ul>.

Angular

export class UserListComponent {
  users: User[] = users;
}
# Your code here

Hint

Make sure the class is exported and the template uses *ngFor to show users.

Practice

1. Why does Angular require TypeScript instead of plain JavaScript?

easy

A. Because TypeScript adds type safety and helps catch errors early

B. Because JavaScript cannot run in browsers

C. Because TypeScript is faster to write than JavaScript

D. Because Angular only supports Microsoft products

Solution

1. Step 1: Understand Angular's need for error checking

   Angular apps are complex and benefit from early error detection to avoid runtime bugs.

2. Step 2: Recognize TypeScript's role

   TypeScript adds type safety and static checks that JavaScript alone does not provide.

3. Final Answer:

   Because TypeScript adds type safety and helps catch errors early -> Option A

4. Quick Check:

   Type safety = A [OK]

Hint: TypeScript catches errors before running code [OK]

Common Mistakes:

• Thinking JavaScript can't run in browsers
• Believing TypeScript is just faster to write
• Assuming Angular only supports Microsoft tech

2. Which of the following is a correct TypeScript feature that Angular uses?

easy

A. Dynamic typing without any type declarations

B. Static typing with interfaces and types

C. Using var instead of let or const

D. Writing HTML inside TypeScript files

Solution

1. Step 1: Identify TypeScript features Angular relies on

   Angular uses static typing to define clear contracts using interfaces and types.

2. Step 2: Eliminate incorrect options

   Dynamic typing is JavaScript's feature, not TypeScript's; var is outdated; HTML is separate from TypeScript.

3. Final Answer:

   Static typing with interfaces and types -> Option B

4. Quick Check:

   Static typing = C [OK]

Hint: TypeScript uses static typing, not dynamic [OK]

Common Mistakes:

• Confusing dynamic typing with static typing
• Using outdated var keyword
• Mixing HTML code inside TypeScript files

3. Consider this Angular TypeScript code snippet:

interface User {
  name: string;
  age: number;
}
function greet(user: User) {
  return `Hello, ${user.name}!`;
}
console.log(greet({ name: 'Anna', age: 30 }));

What will be the output when this code runs?

medium

A. Hello, 30!

B. Hello, undefined!

C. Hello, Anna!

D. Type error at compile time

Solution

1. Step 1: Analyze the interface and function

   The interface requires a name (string) and age (number). The function returns a greeting using user.name.

2. Step 2: Check the function call

   The object passed has name 'Anna' and age 30, matching the interface. The function returns 'Hello, Anna!'.

3. Final Answer:

   Hello, Anna! -> Option C

4. Quick Check:

   Output greeting uses user.name = D [OK]

Hint: Look for string interpolation using user.name [OK]

Common Mistakes:

• Confusing age with name in output
• Expecting runtime error instead of correct output
• Thinking TypeScript errors stop code from running here

4. Identify the error in this Angular TypeScript code:

function addNumbers(a: number, b: number): number {
  return a + b;
}
console.log(addNumbers(5, '10'));

medium

A. Syntax error: missing semicolon

B. No error, outputs 15

C. Runtime error: cannot add number and string

D. Type error: second argument should be a number

Solution

1. Step 1: Check function parameter types

   The function expects two numbers as arguments.

2. Step 2: Analyze the function call

   The second argument is a string '10', which violates the number type requirement, causing a compile-time type error.

3. Final Answer:

   Type error: second argument should be a number -> Option D

4. Quick Check:

   Type mismatch error = A [OK]

Hint: Check argument types match function parameters [OK]

Common Mistakes:

• Assuming string '10' converts automatically
• Expecting runtime error instead of compile-time error
• Ignoring TypeScript type checks

5. You want to create an Angular component that only accepts a title property as a string and a count property as a number. Why is using TypeScript important here?

hard

A. It ensures the component receives correct property types, preventing bugs

B. It automatically styles the component based on property types

C. It allows the component to run without any HTML template

D. It converts the component into a JavaScript library

Solution

1. Step 1: Understand component property typing

   Defining property types helps Angular check that the right data is passed to the component.

2. Step 2: Recognize TypeScript's role in error prevention

   TypeScript catches wrong types early, avoiding bugs and unexpected behavior.

3. Final Answer:

   It ensures the component receives correct property types, preventing bugs -> Option A

4. Quick Check:

   Type safety prevents bugs = B [OK]

Hint: TypeScript enforces correct property types [OK]

Common Mistakes:

• Thinking TypeScript styles components
• Believing components can run without templates
• Confusing TypeScript with packaging tools