Open code, practice, and notes →
Download source with English comments · for reading
TypeScript · 23 Async Functions and Error Types
Series contents · Technology map
Stage: Module Contracts and Plugins · Editable example · Storage ID: typescript-step-23
Goals and learning outcomes
- Use a valid Note without assertions.
- Neither exception form leaves an unhandled failure.
Prerequisites
Work and experiment records from Unit 22, “DOM Types and null Checks”
Key concepts and explanations
Promise Contracts
An async function wraps its result in a Promise. External data still needs structural validation after await.
catch Values
A thrown value is not guaranteed to be an Error. Narrow unknown by checking for Error to create a message.
Practice setup
First check the execution scope guidance on the example screen. The following environment is for extending the assignment in a separate project. Implement it yourself in a separate local project and check it with browser developer tools and tsc --noEmit. Record the installed tsc version in a separate TypeScript project. Enable strict in tsconfig.json and check with tsc --noEmit, then open the runtime exercise using compiled output or a local development server. Do not assume the browser executes TS type annotations directly.
The linked example is a starting point. It does not implement every task below. Complete work beyond its supported scope in a separate project.
Practice tasks
- In async.ts, prepare conditions for a valid response, an Error throw, and a string throw.
- Create a loader returning Promise<Result<Note, string>> and handle Error and string throws.
- Run with a valid response, an Error throw, and a string throw. Results to check: Use a valid Note without assertions. Neither exception form leaves an unhandled failure. Record expected and actual results separately.
Variables to observe
| Variable | Baseline | Change | Expected change / hypothesis |
|---|---|---|---|
| Thrown Value | Error | string | Pre-run hypothesis: both cases will be converted into safe messages. Keep other conditions fixed and record the actual result separately after running. |
Predictions in this table are not measured results. Change one condition at a time and record why the actual result differs.
Completion criteria
- Use a valid Note without assertions.
- Neither exception form leaves an unhandled failure.
Self-check
- Does a return type validate response JSON?
- Why is reading message directly in catch risky?
Official references
Linked example and execution scope
Example source · Runtime environments and limits
The preview is a JavaScript runtime boundary experiment. It does not run TypeScript diagnostics. Check lesson.ts locally with tsc --strict --noEmit --lib ES2023,DOM.
Source code and records are not overwritten automatically. Resetting an existing example also preserves your notes.
Next learning
Previous: DOM Types and null Checks · Next: Modules and type-only import