When are type assertions appropriate?

An assertion overrides the compiler's view of a value. It does not convert the value or validate it. The compiler trusts you, so an incorrect assertion moves a type error into a runtime failure. Assertions are a tool for narrow, well-understood gaps, not a general fix for type errors.

const input = document.getElementById("name") as HTMLInputElement;

const raw: unknown = JSON.parse('{"id":1}');
const data = raw as { id: number };

const routes = ["home", "about"] as const;

Assertion forms and safer alternatives

• as T reinterprets a value as T; the compiler checks that the types overlap
• as const preserves literal types and readonly modifiers
• The non-null assertion ! removes null and undefined without a check
• satisfies checks a value against a type while preserving its inferred type
• Narrowing, a type guard or a schema validator is usually safer than as

The DOM example is reasonable because getElementById returns HTMLElement | null, and the element is known to exist in that markup. The JSON example is not safe: parsing proves only that the text is valid JSON, not that it has an id. For external data, validate the shape instead of asserting it.