What types exist only at compile time in Typescript - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Types that exist only at compile time in TypeScript

Which of the following types exist only during TypeScript's compile time and do not appear in the generated JavaScript code?

A Interfaces and type aliases

B Classes and enums

C Functions and variables

D Objects and arrays

💡 Hint

Think about what TypeScript removes when it compiles to JavaScript.

Interfaces and type aliases are used only for type checking during compile time. They do not produce any JavaScript code.

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

❓ Predict Output

intermediate

Output of TypeScript code with interface

What will be the output when this TypeScript code is compiled and run as JavaScript?

Typescript

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

const user: Person = { name: 'Alice', age: 30 };
console.log(user);

A { name: 'Alice', age: 30 }

B undefined

C Error: Interface Person does not exist at runtime

D ReferenceError: user is not defined

💡 Hint

Interfaces disappear after compilation, but objects remain.

The interface is removed during compilation. The object user remains and is logged as expected.

❓ Predict Output

advanced

Type alias usage and runtime presence

Given this TypeScript code, what will be the output when compiled and run as JavaScript?

Typescript

type ID = number | string;

const userId: ID = 123;
console.log(typeof userId);

A TypeError at runtime

B "ID"

C "string"

D "number"

💡 Hint

Type aliases do not exist at runtime, only the value does.

The type alias ID is removed during compilation. The variable userId holds the number 123, so typeof userId is "number".

🧠 Conceptual

advanced

Which TypeScript constructs are erased at compile time?

Select the TypeScript constructs that are completely erased and do not exist in the emitted JavaScript code.

A Enums and namespaces

B Interfaces and type aliases

C Classes and functions

D Variables and constants

💡 Hint

Think about what is used only for type checking.

Interfaces and type aliases are only for type checking and are removed during compilation.

Enums, namespaces, classes, functions, variables, and constants generate JavaScript code.

🧠 Conceptual

expert

Understanding TypeScript's type system and runtime

Which statement correctly describes the relationship between TypeScript types and JavaScript runtime values?

A Interfaces are converted to JavaScript classes at runtime.

B All TypeScript types exist at runtime as JavaScript objects.

C TypeScript types are only for compile-time checks and do not exist at runtime.

D Type aliases generate JavaScript functions during compilation.

💡 Hint

Consider what happens to types after TypeScript compiles to JavaScript.

TypeScript types are erased after compilation and only help during development for type safety.

Interfaces and type aliases do not produce JavaScript code.

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