Course contentsShow
← TypeScript
Lesson 187 of 1,7964. Type InferenceFree lesson

Generic Inference Falling Back to Unknown

When generic type parameters can't be inferred and default to unknown or constraints.

Generic Inference Falling Back to Unknown

What You'll Learn

You'll learn what happens when TypeScript's generic inference can't figure out a type parameter and defaults to unknown (or the constraint you've set).

The Inference Failure Scenario

Remember how TypeScript infers types automatically? With generics, TypeScript tries to infer what <T> should be based on how you use a function. But sometimes, there's not enough information to make a smart guess.

When inference fails and you haven't provided an explicit type argument, TypeScript has to pick something safe. It won't pick any (that would be dangerous!). Instead, it defaults to:

  • unknown if the generic has no constraint
  • The constraint type if you've set one (like <T extends string>)

A Plain-English Analogy

Imagine ordering a mystery box without specifying what's inside. If the store has zero clues, they might label it "unknown contents" for safety. If you said "it must be a fruit," they'd at least know it's some fruit, even if they don't know which one.

When This Happens

function wrapValue<T>(value: T) {
  return { value };
}

// Called without arguments — no clue what T is!
const result = wrapValue(); // Error: Expected 1 argument

With optional parameters or defaults:

function makeContainer<T>(initial?: T) {
  // T inferred as unknown if you don't pass initial
}

const container = makeContainer(); // T is unknown here

Key Takeaway: When TypeScript can't infer a generic type parameter from usage, it defaults to unknown (or your constraint) to maintain type safety—you may need to provide an explicit type argument like makeContainer<string>().