Bird
Raised Fist0
Typescriptprogramming~5 mins

Global augmentation in Typescript - Time & Space Complexity

Choose your learning style10 modes available
Time Complexity: Global augmentation
O(1)
Understanding Time Complexity

We want to understand how adding new properties or methods to existing types affects the speed of our program.

How does this change the work the program does as input grows?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.


// Add a new method to the Array type
declare global {
  interface Array {
    doubleLength(): number;
  }
}

Array.prototype.doubleLength = function() {
  return this.length * 2;
};

const arr = [1, 2, 3];
console.log(arr.doubleLength());
    

This code adds a new method to all arrays that returns twice their length.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

  • Primary operation: Accessing the array's length property.
  • How many times: Once per method call, no loops or recursion involved.
How Execution Grows With Input

Since the method only reads the length property and multiplies it, the work stays the same no matter how big the array is.

Input Size (n)Approx. Operations
101 simple operation
1001 simple operation
10001 simple operation

Pattern observation: The work does not increase as the array grows.

Final Time Complexity

Time Complexity: O(1)

This means the method runs in constant time regardless of the array size.

Common Mistake

[X] Wrong: "Adding a method to Array makes all array operations slower because it loops over elements."

[OK] Correct: The added method runs only when called, and if it does not loop, it does not slow down other array operations.

Interview Connect

Understanding how extending built-in types affects performance shows you can think about code design and efficiency together.

Self-Check

"What if the new method loops through all array elements? How would the time complexity change?"

Practice

(1/5)
1. What is the main purpose of declare global in TypeScript?
easy
A. To import external modules into the current file
B. To declare a new local variable inside a function
C. To safely add or modify types on global objects or modules
D. To create a new class with global scope

Solution

  1. Step 1: Understand the role of declare global

    This keyword is used inside a module to extend or modify global types safely without changing original files.
  2. Step 2: Compare with other options

    Options B, C, and D describe unrelated TypeScript features like local variables, imports, or classes.
  3. Final Answer:

    To safely add or modify types on global objects or modules -> Option C
  4. Quick Check:

    declare global = add/modify global types [OK]
Hint: Remember: declare global extends global types safely [OK]
Common Mistakes:
  • Confusing declare global with import statements
  • Thinking it declares local variables
  • Assuming it creates new classes
2. Which syntax correctly starts a global augmentation block inside a module in TypeScript?
easy
A. declare global { interface Window { customProp: string; } }
B. global declare { interface Window { customProp: string; } }
C. declare module global { interface Window { customProp: string; } }
D. module global declare { interface Window { customProp: string; } }

Solution

  1. Step 1: Identify correct syntax for global augmentation

    The correct syntax uses declare global { ... } inside a module to augment global types.
  2. Step 2: Check other options for syntax errors

    Options A, B, and C use incorrect order or keywords that are invalid in TypeScript.
  3. Final Answer:

    declare global { interface Window { customProp: string; } } -> Option A
  4. Quick Check:

    declare global { ... } is correct syntax [OK]
Hint: Use 'declare global { }' exactly to augment globals [OK]
Common Mistakes:
  • Swapping 'declare' and 'global' keywords
  • Using 'declare module global' incorrectly
  • Missing curly braces after declare global
3. What will be the output of this TypeScript code after global augmentation?
export {};
declare global {
  interface Array<T> {
    first(): T | undefined;
  }
}

Array.prototype.first = function() {
  return this.length > 0 ? this[0] : undefined;
};

const nums = [10, 20, 30];
console.log(nums.first());
medium
A. undefined
B. 30
C. Error: Property 'first' does not exist on type 'number[]'
D. 10

Solution

  1. Step 1: Understand the global augmentation of Array interface

    The code adds a new method first() to all arrays returning the first element or undefined if empty.
  2. Step 2: Analyze the output of calling nums.first()

    The array nums has elements [10, 20, 30], so first() returns 10, the first element.
  3. Final Answer:

    10 -> Option D
  4. Quick Check:

    nums.first() = 10 [OK]
Hint: Augmented methods work like normal after declaration [OK]
Common Mistakes:
  • Expecting a TypeScript error without module context
  • Thinking first() returns undefined always
  • Confusing first element with last element
4. Identify the error in this global augmentation code and fix it:
declare global {
  interface String {
    shout(): string;
  }
}

String.prototype.shout = function() {
  return this.toUpperCase() + "!";
};
medium
A. Cannot augment String interface globally
B. Missing export {} to make file a module
C. Incorrect method name, should be 'shoutOut'
D. Prototype assignment must be inside declare global block

Solution

  1. Step 1: Check module context requirement for global augmentation

    Global augmentation requires the file to be a module, so it needs an export {} or import statement.
  2. Step 2: Identify missing export statement

    The code lacks export {}, so TypeScript treats it as a script, causing errors with declare global.
  3. Final Answer:

    Missing export {} to make file a module -> Option B
  4. Quick Check:

    File must be a module for declare global [OK]
Hint: Add 'export {}' to enable global augmentation [OK]
Common Mistakes:
  • Forgetting to make file a module
  • Trying to assign prototype inside declare global
  • Renaming methods unnecessarily
5. You want to add a global method logInfo() to the console object that prefixes messages with '[INFO]'. Which is the correct way to augment the global Console interface and implement this method?
hard
A. export {}; declare global { interface Console { logInfo(message: string): void; } } console.logInfo = (msg) => console.log(`[INFO] ${msg}`);
B. declare module 'console' { interface Console { logInfo(message: string): void; } } console.logInfo = (msg) => console.log(`[INFO] ${msg}`);
C. declare global { interface Console { logInfo(message: string): void; } } console.prototype.logInfo = function(msg) { console.log(`[INFO] ${msg}`); };
D. export {}; declare global { interface Console { logInfo(message: string): void; } } console.prototype.logInfo = (msg) => console.log(`[INFO] ${msg}`);

Solution

  1. Step 1: Correctly augment the global Console interface

    Use export {} to make the file a module, then declare global with interface Console adding logInfo.
  2. Step 2: Properly assign the method to console object

    Assign console.logInfo directly, not on console.prototype because console is an object, not a class instance.
  3. Final Answer:

    export {}; declare global { interface Console { logInfo(message: string): void; } } console.logInfo = (msg) => console.log(`[INFO] ${msg}`); -> Option A
  4. Quick Check:

    Use declare global + direct console method assignment [OK]
Hint: Augment interface then assign method directly on console [OK]
Common Mistakes:
  • Using declare module 'console' instead of declare global
  • Assigning method to console.prototype (wrong for object)
  • Forgetting export {} to make file a module
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard