What types exist only at compile time in Typescript

Introduction

Some types in TypeScript help check your code while you write it but disappear when the program runs. This keeps your code safe without slowing it down.

When you want to catch mistakes before running your code.

When you want to describe the shape of data without adding extra code.

When you want to use types for checking but not affect the final program size.

When you want to create reusable type rules that help during coding only.

Syntax

Typescript

type MyType = string | number;
interface MyInterface {
  name: string;
  age: number;
}

// These types exist only during compile time and are removed in JavaScript output.

Types and interfaces are erased after TypeScript checks your code.

They do not create any JavaScript code or affect runtime performance.

Examples

This defines a type and an interface used only to check code before running.

Typescript

type ID = number | string;

interface User {
  id: ID;
  name: string;
}

The type Point helps check the function input but disappears in the final JavaScript.

Typescript

type Point = { x: number; y: number };

function printPoint(p: Point) {
  console.log(`x: ${p.x}, y: ${p.y}`);
}

Sample Program

This program uses types and interfaces to check data shapes before running. The types do not exist in the JavaScript output.

Typescript

type Age = number;

interface Person {
  name: string;
  age: Age;
}

function greet(person: Person) {
  console.log(`Hello, ${person.name}. You are ${person.age} years old.`);
}

const user = { name: "Alice", age: 30 };
greet(user);

Important Notes

Types and interfaces are only for the developer and compiler, not for the running program.

Using these compile-time types helps find errors early without adding extra code.

Summary

Types and interfaces exist only at compile time in TypeScript.

They help catch errors and describe data shapes but do not create JavaScript code.

This keeps your final program fast and clean.

Practice

1. Which of the following TypeScript types exist only at compile time and do not produce any JavaScript code?

easy

A. Functions and variables

B. Classes and enums

C. Interfaces and type aliases

D. Objects and arrays

Solution

1. Step 1: Understand TypeScript compile-time types

   Interfaces and type aliases are used only to check types during compilation and do not exist in the final JavaScript.

2. Step 2: Identify runtime constructs

   Classes, enums, functions, variables, objects, and arrays exist in the JavaScript output and run at runtime.

3. Final Answer:

   Interfaces and type aliases -> Option C

4. Quick Check:

   Compile-time only types = Interfaces, type aliases [OK]

Hint: Remember: interfaces and types vanish after compiling [OK]

Common Mistakes:

• Thinking classes are compile-time only
• Confusing enums with type aliases
• Assuming variables are compile-time types

2. Which syntax correctly declares a type alias that exists only at compile time in TypeScript?

easy

A. type User = { name: string; age: number };

B. const User = { name: 'Alice', age: 30 };

C. class User { name: string; age: number; }

D. enum User { Name, Age }

Solution

1. Step 1: Identify type alias syntax

   Using type User = { ... } declares a type alias that exists only during compilation.

2. Step 2: Differentiate from runtime declarations

   Const objects, classes, and enums produce JavaScript code and exist at runtime.

3. Final Answer:

   type User = { name: string; age: number }; -> Option A

4. Quick Check:

   Type alias syntax = type ... = ... [OK]

Hint: Type aliases start with 'type' keyword [OK]

Common Mistakes:

• Using const or class instead of type alias
• Confusing enums with types
• Missing semicolon in type alias

3. What will be the output of the following TypeScript code when compiled and run in JavaScript?

interface Person { name: string; age: number; }
const p: Person = { name: 'Bob', age: 25 };
console.log(typeof Person);

medium

A. "undefined"

B. "object"

C. "function"

D. "string"

Solution

1. Step 1: Understand interface removal at compile time

   Interfaces do not exist in JavaScript output, so Person is not defined at runtime.

2. Step 2: Evaluate typeof on undefined identifier

   Using typeof Person when Person is not defined returns "undefined" as a string.

3. Final Answer:

   "undefined" -> Option A

4. Quick Check:

   Interfaces vanish, typeof interface = "undefined" [OK]

Hint: Interfaces disappear; typeof interface is undefined [OK]

Common Mistakes:

• Expecting 'object' because of interface
• Thinking interface is a function
• Confusing interface with class

4. Identify the error in this TypeScript code snippet:

type Animal = { species: string };
console.log(Animal);

medium

A. Missing semicolon after type declaration

B. Animal should be declared as an interface

C. Type alias syntax is incorrect

D. Animal is not defined at runtime, so console.log causes an error

Solution

1. Step 1: Recognize type alias compile-time only nature

   Type aliases do not exist in JavaScript, so Animal is not a runtime value.

2. Step 2: Understand console.log usage

   Trying to log Animal causes a runtime error because it is undefined in JavaScript.

3. Final Answer:

   Animal is not defined at runtime, so console.log causes an error -> Option D

4. Quick Check:

   Logging type alias = runtime error [OK]

Hint: Type aliases can't be used as runtime values [OK]

Common Mistakes:

• Thinking type aliases exist at runtime
• Ignoring runtime vs compile-time difference
• Assuming missing semicolon causes error

5. You want to create a function that accepts only objects matching a specific shape but does not add any runtime overhead. Which TypeScript feature should you use?

hard

A. Use a type alias and create a runtime object

B. Use an interface to define the object shape

C. Use a class to define the object shape

D. Use an enum to define the object shape

Solution

1. Step 1: Understand compile-time type checking

   Interfaces define object shapes only at compile time and do not generate JavaScript code, so no runtime overhead.

2. Step 2: Compare with other options

   Classes and enums generate runtime code; type aliases do not create runtime objects unless explicitly instantiated.

3. Final Answer:

   Use an interface to define the object shape -> Option B

4. Quick Check:

   Interfaces = compile-time only, no runtime overhead [OK]

Hint: Interfaces check shape without runtime cost [OK]

Common Mistakes:

• Using classes which add runtime code
• Confusing enums with object shapes
• Thinking type aliases create runtime objects