Why TypeScript is required in Angular - Performance Evidence

Performance: Why TypeScript is required in Angular

MEDIUM IMPACT

Using TypeScript in Angular affects the build time and bundle size, impacting initial load speed and developer productivity.

Writing Angular components with type safety and modern features

Angular

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

@Component({
  selector: 'app-root',
  template: `<h1>{{title}}</h1>`
})
export class AppComponent {
  title: string = 'Hello Angular';
}

TypeScript provides static typing and modern features, catching errors at compile time and improving code maintainability.

📈 Performance GainReduces runtime errors and debugging time, improving developer efficiency and app stability.

Writing Angular components with type safety and modern features

Angular

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

@Component({
  selector: 'app-root',
  template: `<h1>{{title}}</h1>`
})
export class AppComponent {
  title = 'Hello Angular';
}

Using plain JavaScript without TypeScript means no static type checking, leading to more runtime errors and harder debugging.

📉 Performance CostIncreases debugging time and potential runtime errors, indirectly affecting user experience.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
JavaScript without TypeScript	No impact	No impact	No impact	[!] OK but error-prone
Angular with TypeScript	No impact	No impact	No impact	[OK] Better code quality

Rendering Pipeline

TypeScript code is compiled to JavaScript before the browser runs it. This compilation step happens during build time, not runtime, so it does not directly affect rendering but influences bundle size and load time.

→Build Time

→Network Transfer

→Parsing & Execution

⚠️ BottleneckBuild Time and Bundle Size

Core Web Vital Affected

LCP

Using TypeScript in Angular affects the build time and bundle size, impacting initial load speed and developer productivity.

Optimization Tips

1TypeScript adds compile-time checks but slightly increases build time and bundle size.

2Use AOT compilation to optimize Angular app load performance.

3Static typing reduces runtime errors, improving user experience indirectly.

Performance Quiz - 3 Questions

How does using TypeScript in Angular affect page load performance?

A It directly slows down browser rendering by adding runtime overhead.

B It increases build time and bundle size slightly, affecting initial load speed.

C It reduces bundle size significantly, speeding up load time.

D It has no effect on performance at all.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and check the size of main JavaScript bundles.

What to look for: Look for bundle size and load time; smaller bundles load faster, improving LCP.

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