What Index Signatures Solve
You'll learn: Why TypeScript needs a special syntax to handle objects with unpredictable property names while maintaining type safety.
The Problem with Dynamic Property Names
So far, you've worked with objects where you know every property name in advance:
const user = {
name: "Alice",
age: 30
};
But what if you're building a dictionary, a cache, or a configuration object where you don't know which keys will exist ahead of time?
In JavaScript, this is trivial — just add whatever properties you want. But in TypeScript, you can't safely access properties that weren't declared in the type.
Real-World Scenarios
Think of these common patterns:
- Translation dictionaries:
{ "en": "Hello", "es": "Hola", "fr": "Bonjour" }— you don't know every language code upfront - User preferences by ID:
{ "user123": true, "user456": false }— user IDs are dynamic - API response data: Keys might vary based on runtime conditions
Without index signatures, TypeScript would force you to declare every single possible property name — completely impractical for dynamic data.
The Type Safety Gap
Index signatures bridge this gap by letting you say: "This object can have any number of properties with this key type and this value type."
You get the flexibility of JavaScript's dynamic objects while still enforcing that all values match a specific type — no random strings where you expect numbers, no undefined runtime surprises.
Key Takeaway: Index signatures solve the problem of typing objects with arbitrary or runtime-determined property names, providing type safety for values without requiring you to enumerate every possible key.