TypeScript Strict Mode and Why It Matters - Time & Space Complexity

Time Complexity: TypeScript Strict Mode and Why It Matters

O(n)

Understanding Time Complexity

We want to understand how turning on TypeScript's strict mode affects the time it takes to check code as it grows.

How does strict mode change the work the compiler does when code gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following TypeScript code with strict mode enabled.

function sumNumbers(numbers: number[]): number {
  let total = 0;
  for (const num of numbers) {
    total += num;
  }
  return total;
}

const values = [1, 2, 3, 4, 5];
console.log(sumNumbers(values));
    

This code sums numbers in an array, with strict mode checking types carefully.

Identify Repeating Operations

Look at what repeats as input grows.

• Primary operation: Looping through each number in the array.
• How many times: Once for each item in the input array.

How Execution Grows With Input

As the array gets bigger, the compiler checks each item one by one.

Input Size (n)	Approx. Operations
10	About 10 checks
100	About 100 checks
1000	About 1000 checks

Pattern observation: The work grows directly with the number of items.

Final Time Complexity

Time Complexity: O(n)

This means the time to check the code grows in a straight line as the input size grows.

Common Mistake

[X] Wrong: "Strict mode makes the compiler slow in a way that grows faster than the code size."

[OK] Correct: Strict mode adds checks, but these checks happen once per item, so the growth stays proportional to input size, not worse.

Interview Connect

Understanding how strict mode affects checking time helps you write safer code without surprises about performance as your projects grow.

Self-Check

"What if we added nested objects in the array? How would strict mode's time complexity change?"

Practice

1. What is the main purpose of enabling strict mode in TypeScript?

easy

A. To allow JavaScript code to run without any type checking

B. To make TypeScript run faster by skipping type checks

C. To make TypeScript check your code more carefully and catch errors early

D. To disable all compiler warnings and errors

Solution

1. Step 1: Understand what strict mode does

   Strict mode in TypeScript enables more thorough type checking to find mistakes early.

2. Step 2: Compare options with strict mode purpose

   Only To make TypeScript check your code more carefully and catch errors early correctly describes strict mode as making TypeScript check code carefully and catch errors early.

3. Final Answer:

   To make TypeScript check your code more carefully and catch errors early -> Option C

4. Quick Check:

   Strict mode = careful checks [OK]

Hint: Strict mode means more checks, fewer bugs [OK]

Common Mistakes:

• Thinking strict mode disables checks
• Confusing strict mode with performance settings
• Believing strict mode allows ignoring types

2. Which setting in tsconfig.json enables strict mode in TypeScript?

easy

A. "strictCheck": true

B. "strict": true

C. "enableStrict": true

D. "typeCheck": true

Solution

1. Step 1: Identify the correct tsconfig.json key for strict mode

   The official key to enable strict mode is "strict" set to true.

2. Step 2: Eliminate incorrect options

   Options A, B, and C are not valid TypeScript compiler options for strict mode.

3. Final Answer:

   "strict": true -> Option B

4. Quick Check:

   Strict mode key = "strict" [OK]

Hint: Look for "strict": true in tsconfig.json [OK]

Common Mistakes:

• Using incorrect keys like "strictCheck"
• Confusing strict mode with other compiler options
• Forgetting to put the key inside tsconfig.json

3. What will happen if you run this TypeScript code with strict mode enabled?

let name: string;
console.log(name.length);

medium

A. It will cause a compile-time error because 'name' is used before being assigned

B. It will print the length of the string

C. It will print 'undefined'

D. It will run without errors and print 0

Solution

1. Step 1: Understand variable initialization in strict mode

   With strict mode, TypeScript requires variables to be initialized before use.

2. Step 2: Analyze the code behavior

   The variable 'name' is declared but not assigned a value before accessing 'name.length', causing a compile-time error.

3. Final Answer:

   It will cause a compile-time error because 'name' is used before being assigned -> Option A

4. Quick Check:

   Uninitialized variable use = error [OK]

Hint: Uninitialized variables cause errors in strict mode [OK]

Common Mistakes:

• Assuming variables default to empty string
• Thinking code runs without errors
• Confusing runtime errors with compile-time errors

4. Identify the error in this TypeScript code when strict mode is enabled and fix it:

function greet(name: string | undefined) {
  console.log(name.toUpperCase());
}

medium

A. Error: 'name' might be undefined; fix by checking if 'name' exists before calling toUpperCase()

B. Error: 'toUpperCase' is not a function; fix by casting 'name' to string

C. No error, code is correct

D. Error: Missing return type; fix by adding ': void' to function

Solution

1. Step 1: Understand strict null checks

   With strict mode, TypeScript requires checking if a variable that can be undefined is actually defined before using it.

2. Step 2: Identify the error and fix

   Calling 'toUpperCase()' on 'name' without checking if it's undefined causes an error. Fix by adding a check like 'if (name)'.

3. Final Answer:

   Error: 'name' might be undefined; fix by checking if 'name' exists before calling toUpperCase() -> Option A

4. Quick Check:

   Check undefined before method call [OK]

Hint: Check for undefined before using variable methods [OK]

Common Mistakes:

• Ignoring possible undefined values
• Trying to cast without checks
• Assuming no error without strict mode

5. You have this TypeScript code with strict mode enabled:

interface User {
  id: number;
  name?: string;
}

function printUserName(user: User) {
  console.log(user.name.toUpperCase());
}

How can you fix the code to avoid errors and safely print the user's name in uppercase if it exists?

hard

A. Assign a default value: console.log((user.name || '').toUpperCase());

B. Remove the question mark from 'name' in interface to make it required

C. Use a non-null assertion: console.log(user.name!.toUpperCase());

D. Add a check: if (user.name) console.log(user.name.toUpperCase());

Solution

1. Step 1: Understand optional properties and strict mode

   The 'name' property is optional, so it can be undefined. Strict mode requires checking before use.

2. Step 2: Evaluate options to safely access 'name'

   Add a check: if (user.name) console.log(user.name.toUpperCase()); safely checks if 'name' exists before calling 'toUpperCase()', avoiding errors. Options B, C, and D have drawbacks or risks.

3. Final Answer:

   Add a check: if (user.name) console.log(user.name.toUpperCase()); -> Option D

4. Quick Check:

   Check optional before use = safe code [OK]

Hint: Check optional properties before use in strict mode [OK]

Common Mistakes:

• Using non-null assertion without guarantee
• Assuming optional properties are always defined
• Removing optional marker without reason