Typing the this Parameter
Understand Typing the this Parameter
A this parameter annotation declares the expected receiver for an ordinary function. It appears first in the parameter list but is erased from JavaScript output.
What you will learn: the purpose of typing the this parameter, the rules TypeScript checks, and what its JavaScript behavior looks like in a runnable example.
What you’ll learn
- Explain how typing the this parameter works and where its type rules apply.
- Predict the exact output of the typing the this parameter example.
- Diagnose a common issue: Do not call withTax(0.
Build the mental model
In strict JavaScript, this normally depends on how a function is called. TypeScript lets you describe that requirement; the annotation does not bind a receiver at runtime. Use call, apply, bind, or method-call syntax to provide the actual receiver. Arrow functions do not have a dynamic this.
Key distinction: TypeScript checks the declared types during development; emitted JavaScript carries out the value-level operation at runtime. A type declaration alone never validates untrusted runtime input.
See the relationship
Read this illustration from the first labeled part to the last. Compare it with the example and identify which parts are type checks and which parts run in JavaScript.
Run the complete TypeScript example
This self-contained example uses fixed values, so it runs without reading input or depending on an external service. Paste it into the TypeScript Playground or save it as main.ts.
TypeScript program
type Cart = { subtotal: number };
function withTax(this: Cart, rate: number): number {
return this.subtotal * (1 + rate);
}
const cart: Cart = { subtotal: 200 };
console.log(withTax.call(cart, 0.1).toFixed(2));Verified output
220.00Run locally: npx tsc --strict --target es2022 --module commonjs main.ts, then node main.js. For projects with a tsconfig.json, build using that configuration instead.
Trace every important step
The function declares that this must have a subtotal number. The call method supplies cart as the runtime receiver and 0.1 as the rate. The numeric result is approximately 220, and toFixed(2) displays 220.00.
Check each step: identify the input values, follow the JavaScript operation in execution order, and match the final expression with the exact output shown. An annotation can reject invalid source before execution, but does not change the value printed.
Avoid these common mistakes
Do not call withTax(0.1) without a receiver. The annotation does not inject a this value, and calling a detached method can lose its intended receiver.
How to debug: reproduce the issue in a minimal example. For compiler errors, inspect the inferred and declared types; for a runtime surprise, log the actual values and follow their references or branches.
Practice and experiment
Change cart.subtotal to 80 and use withTax.call(cart, 0.05). Explain why this is absent from the emitted function parameter list.
Practice routine: predict the result on paper, edit one part of the code, compile under --strict, run the JavaScript, and explain whether TypeScript caught an error or JavaScript simply behaved differently.
Check your understanding
Review the key idea
Typing the this Parameter: A this parameter annotation declares the expected receiver for an ordinary function.
The function declares that this must have a subtotal number. The call method supplies cart as the runtime receiver and 0.1 as the rate. The numeric result is approximately 220, and toFixed(2) displays 220.00.
Before continuing, explain one valid use case, one common pitfall, and the separation between compile-time checking and runtime behavior for this feature.
Reaching the recap and completing the quizzes are separate milestones.