Der any-Typ und warum Sie ihn vermeiden sollten

Willkommen

Was any bewirkt

let x: any = 5;
x = 'hello';       // OK
x = true;          // OK
x.nonExistent();   // No error — but crashes at runtime!

Wie sich any ausbreitet

let data: any = fetchData();
let name: string = data.name; // name is now effectively any

Wann TypeScript any ableitet

let value; // inferred as any — dangerous!
value = 42;
value = 'hello';

// Fix:
let value2: number;

Das noImplicitAny-Flag

// tsconfig.json
{ "compilerOptions": { "noImplicitAny": true } }

// Now this is an error:
function process(data) { } // Error: Parameter has implicit any type

Berechtigte Verwendungen von any

// Acceptable: narrow scope, clearly documented
function parseJson(raw: string): any {
  return JSON.parse(raw); // validate with Zod afterwards
}

Typassertionen als Alternative

const raw = JSON.parse(text) as { name: string; age: number };
console.log(raw.name); // typed correctly

any vs. object

let o: object = { x: 1 };
// o.x; // Error — object doesn't allow property access

let a: any = { x: 1 };
a.x; // OK — but no safety

any deaktiviert die Autovervollständigung

any durch unknown ersetzen

let input: unknown = getInput();
// input.toUpperCase(); // Error — must narrow first
if (typeof input === 'string') {
  console.log(input.toUpperCase()); // OK
}

Das any-Budget

Schnelltest

Zusammenfassung