Type erasure and its consequences in Typescript

Introduction

Type erasure means TypeScript removes all type information when it turns your code into JavaScript. This helps your code run in any browser or environment that understands JavaScript.

When you want to write safer code with types but still run it anywhere JavaScript runs.

When you use generics to write reusable functions or classes but don't want types to affect runtime.

When debugging, to understand why type info is missing in the running code.

When integrating TypeScript code with plain JavaScript libraries or tools.

Syntax

Typescript

function identity<T>(arg: T): T {
  return arg;
}

Type parameters like <T> exist only during development and are removed in the final JavaScript.

At runtime, TypeScript code behaves like plain JavaScript without type checks.

Examples

This generic function returns whatever you give it. The T is a placeholder for any type.

Typescript

function identity<T>(arg: T): T {
  return arg;
}

Here, we tell TypeScript that T is a number. But at runtime, this is just identity(42).

Typescript

const result = identity<number>(42);
console.log(result);

Type erasure means you can't check types at runtime, so you must be careful with properties that might not exist.

Typescript

function logLength<T>(arg: T): T {
  // console.log(arg.length); // Error: length might not exist
  return arg;
}

Sample Program

This program shows a generic function that returns the input. Types help during coding but disappear when running.

Typescript

function identity<T>(arg: T): T {
  return arg;
}

const num = identity<number>(123);
const str = identity<string>("hello");

console.log(num);
console.log(str);

Important Notes

Type erasure means you cannot use types to check or change behavior at runtime.

Be careful with assumptions about types when your code runs, because type info is gone.

Use runtime checks (like typeof) if you need to verify types while running.

Summary

TypeScript removes all type info when creating JavaScript code.

Types help you write safer code but do not exist when the code runs.

You must use JavaScript checks if you want to test types at runtime.

Practice

1. What does type erasure mean in TypeScript?

easy

A. TypeScript removes all type information when compiling to JavaScript.

B. TypeScript keeps all type information in the final JavaScript code.

C. TypeScript converts types into runtime checks automatically.

D. TypeScript adds extra type annotations in the JavaScript output.

Solution

1. Step 1: Understand TypeScript compilation

   TypeScript compiles to JavaScript by removing all type annotations and interfaces.

2. Step 2: Define type erasure meaning

   This removal of type info is called type erasure, meaning types exist only during development, not at runtime.

3. Final Answer:

   TypeScript removes all type information when compiling to JavaScript. -> Option A

4. Quick Check:

   Type erasure = types removed at compile time [OK]

Hint: Remember: TypeScript types vanish in JavaScript output [OK]

Common Mistakes:

• Thinking types exist at runtime
• Believing TypeScript adds runtime type checks
• Confusing type erasure with type inference

2. Which of the following is the correct way to check a variable's type at runtime in TypeScript?

easy

A. Using typeof operator in JavaScript code.

B. Using TypeScript type annotations like string in if statements.

C. Using TypeScript interfaces to check types at runtime.

D. Using instanceof with TypeScript types.

Solution

1. Step 1: Recall type erasure effect

   TypeScript types do not exist at runtime, so you cannot use them in runtime checks.

2. Step 2: Identify runtime type check method

   JavaScript's typeof operator works at runtime to check primitive types like string or number.

3. Final Answer:

   Using typeof operator in JavaScript code. -> Option A

4. Quick Check:

   Runtime type check = typeof operator [OK]

Hint: Use JavaScript's typeof for runtime type checks [OK]

Common Mistakes:

• Trying to use TypeScript types at runtime
• Using interfaces for runtime checks
• Confusing instanceof with TypeScript types

3. What will be the output of this TypeScript code after compilation and running in JavaScript?

function isString(value: any): boolean {
  return typeof value === 'string';
}

console.log(isString(123));
console.log(isString('hello'));

medium

A. true\ntrue

B. false\nfalse

C. false\ntrue

D. TypeError at runtime

Solution

1. Step 1: Understand the function logic

   The function returns true if the input's JavaScript type is 'string', false otherwise.

2. Step 2: Evaluate the calls

   For 123, typeof is 'number', so returns false. For 'hello', typeof is 'string', so returns true.

3. Final Answer:

   false\ntrue -> Option C

4. Quick Check:

   typeof 123 = number (false), typeof 'hello' = string (true) [OK]

Hint: Check typeof results for each input value [OK]

Common Mistakes:

• Assuming TypeScript types affect runtime
• Expecting true for number input
• Confusing output order

4. Identify the error in this TypeScript code that tries to check if value is a number at runtime:

function checkNumber(value: any): boolean {
  if (value instanceof number) {
    return true;
  }
  return false;
}

medium

A. The function should use typeof value === 'number' instead.

B. The function should use value.constructor === Number.

C. The function is correct and will return true for numbers.

D. Using instanceof with a primitive type causes a runtime error.

Solution

1. Step 1: Understand instanceof usage

   instanceof works with objects, not primitive types like number.

2. Step 2: Identify error cause

   Using value instanceof number causes a runtime error because number is not a constructor function.

3. Final Answer:

   Using instanceof with a primitive type causes a runtime error. -> Option D

4. Quick Check:

   instanceof with primitives = error [OK]

Hint: Use typeof for primitives, not instanceof [OK]

Common Mistakes:

• Using instanceof with primitive types
• Thinking instanceof works like typeof
• Ignoring runtime errors from wrong instanceof usage

5. Given that TypeScript types are erased at runtime, how can you safely handle different input types in a function that accepts string | number and returns their length or value doubled?

function process(input: string | number) {
  // What is the best way to handle types here?
}

hard

A. Rely on TypeScript types only and assume input is always correct at runtime.

B. Use JavaScript runtime checks like typeof to distinguish types and process accordingly.

C. Use instanceof to check if input is a string or number.

D. Convert input to string and always return its length.

Solution

1. Step 1: Recall type erasure impact

   TypeScript types do not exist at runtime, so runtime checks must use JavaScript operators.

2. Step 2: Choose correct runtime check

   Using typeof lets you detect if input is 'string' or 'number' and handle each case safely.

3. Step 3: Avoid incorrect methods

   Relying only on TypeScript types or using instanceof with primitives is unsafe or incorrect.

4. Final Answer:

   Use JavaScript runtime checks like typeof to distinguish types and process accordingly. -> Option B

5. Quick Check:

   Runtime type safety = typeof checks [OK]

Hint: Always check types at runtime with typeof for unions [OK]

Common Mistakes:

• Assuming TypeScript types exist at runtime
• Using instanceof with primitives
• Ignoring runtime type checks