Type-only imports and exports in Typescript - Time & Space Complexity

Time Complexity: Type-only imports and exports

O(1)

Understanding Time Complexity

We want to understand how using type-only imports and exports affects the time it takes for TypeScript to process code.

Specifically, we ask: does importing or exporting only types change how the program runs as it grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Importing only types
import type { User, Product } from './models';

// Exporting only types
export type { User, Product };

function processUser(user: User) {
  // some logic here
}

This code imports and exports only types without bringing in any runtime code.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: There are no loops or repeated operations here because type-only imports do not generate runtime code.
• How many times: The operations happen once during compile time for type checking, not during program execution.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	Small number of type checks, no runtime cost
100	More type checks, still no runtime cost
1000	Many type checks, but runtime execution remains unaffected

Pattern observation: The compile-time work grows with the number of types, but runtime execution time stays the same.

Final Time Complexity

Time Complexity: O(1)

This means the runtime cost does not grow with the number of type-only imports or exports because they are removed before running.

Common Mistake

[X] Wrong: "Importing many types will slow down my program when it runs."

[OK] Correct: Type-only imports are erased during compilation, so they do not add any runtime cost or slow down the program.

Interview Connect

Understanding how type-only imports affect performance shows you know the difference between compile-time and runtime, a key skill in TypeScript development.

Self-Check

"What if we changed type-only imports to regular imports? How would the time complexity change at runtime?"

Practice

1. What is the main purpose of using import type in TypeScript?

easy

A. To export types from a module.

B. To import both types and runtime values together.

C. To import only runtime values and ignore types.

D. To import only types without including any runtime code.

Solution

1. Step 1: Understand the role of import type

   This syntax imports only type information, not actual code that runs.

2. Step 2: Compare with normal imports

   Normal imports bring in both types and runtime code, but import type excludes runtime code.

3. Final Answer:

   To import only types without including any runtime code. -> Option D

4. Quick Check:

   Type-only imports = import type [OK]

Hint: Remember: import type brings types only, no code. [OK]

Common Mistakes:

• Thinking import type imports runtime code
• Confusing import type with normal import
• Using import type to export types

2. Which of the following is the correct syntax to export only types from a TypeScript module?

easy

A. export { MyType } from './types';

B. export type { MyType } from './types';

C. export import type MyType from './types';

D. export only type MyType from './types';

Solution

1. Step 1: Identify correct export type syntax

   TypeScript uses export type { ... } to export only types.

2. Step 2: Check other options

   export { MyType } from './types'; (export { MyType } from './types';) exports both types and values. Options B and C are invalid syntax.

3. Final Answer:

   export type { MyType } from './types'; -> Option B

4. Quick Check:

   Type-only export = export type [OK]

Hint: Use export type {} to export types only. [OK]

Common Mistakes:

• Using normal export instead of export type
• Writing invalid syntax like export only type
• Confusing import syntax with export syntax

3. Consider the following code snippet:

import type { User } from './models';

function greet(user: User) {
  console.log(`Hello, ${user.name}`);
}

greet({ name: "Alice" });

What will happen when this code is compiled and run?

medium

A. It will print 'Hello, ' followed by the user's name at runtime.

B. It will cause a runtime error because User is not imported as code.

C. It will fail to compile because import type cannot be used with functions.

D. It will import the full User class including methods.

Solution

1. Step 1: Understand import type usage

   The import type imports only type info, which is erased at runtime.

2. Step 2: Check runtime behavior

   The function uses User only as a type for parameter. At runtime, it expects an object with a name property.

3. Final Answer:

   It will print 'Hello, ' followed by the user's name at runtime. -> Option A

4. Quick Check:

   Type-only import works for typing, no runtime error [OK]

Hint: Type-only imports vanish at runtime but keep type safety. [OK]

Common Mistakes:

• Expecting runtime import of types
• Thinking import type causes runtime errors
• Confusing compile-time types with runtime values

4. Identify the error in this TypeScript code:

import type { Config } from './config';

export { Config };

medium

A. You cannot export a type that was imported with import type.

B. The import type statement is missing a semicolon.

C. You must use export type { Config } to export the type correctly.

D. There is no error; this code works fine.

Solution

1. Step 1: Check import and export compatibility

   Types imported with import type must be exported with export type.

2. Step 2: Identify correct export syntax

   Using normal export { Config } tries to export a runtime value, which does not exist.

3. Final Answer:

   You must use export type { Config } to export the type correctly. -> Option C

4. Quick Check:

   Type-only export matches type-only import [OK]

Hint: Match import type with export type. [OK]

Common Mistakes:

• Exporting type-only imports as normal exports
• Ignoring that types do not exist at runtime
• Confusing semicolon errors with syntax errors

5. You have a module shapes.ts exporting types and values:

export type Circle = { radius: number };
export const PI = 3.14;

You want to import only the type Circle in another file without importing PI. Which is the best way?

hard

A. import type { Circle } from './shapes';

B. import { Circle } from './shapes';

C. import { Circle, PI } from './shapes';

D. import type { Circle, PI } from './shapes';

Solution

1. Step 1: Understand import type behavior

   import type imports only types, no runtime values like PI.

2. Step 2: Check options for importing only Circle

   import type { Circle } from './shapes'; imports only the type Circle without bringing in PI.

3. Final Answer:

   import type { Circle } from './shapes'; -> Option A

4. Quick Check:

   Use import type to avoid importing values [OK]

Hint: Use import type to import only types, no values. [OK]

Common Mistakes:

• Using normal import and importing unwanted values
• Trying to import values with import type
• Importing both types and values when only types are needed