Courses
TypeScript Advanced: Types That Hold Up in Production
Check Yourself: Declare What JavaScript Didn't
Five scenario questions on declaration files, ambient modules and augmentation. If you miss more than one, reread the lessons in this section.
Course content
Join this Course
Sign in to save your progress.
-
Types That Compute
-
Conditional Types and infer Without Nested Nightmares
-
Template Literal Types for Routes and Event Names
-
-
-
Brands and Boundaries
-
Branded Types So IDs Don't Mix
-
satisfies and const Assertions When Inference Isn't Enough
-
-
-
Declare What JavaScript Didn't
-
Writing .d.ts for a Plain JS Module
-
Ambient Modules and Global Augmentation Without Breaking Everything
-
-
-
Projects That Scale
-
Project References and Solution-Style tsconfig
-
typescript-eslint Rules That Catch Real Mistakes
-
-
-
Migrate and Keep Moving
-
Move a JavaScript Folder to TypeScript Without a Big Bang
-
allowJs, checkJs and Leaving JSDoc Behind
-
Keep Build Times Sane: incremental and What Actually Slows tsc
-
-
- Final Check: TypeScript Advanced
1.
You import a relative path to a plain JavaScript file in strict mode and see error TS7016. What is the best fix?
2.
A hand-written .d.ts says a function returns a string, and the JavaScript actually returns a number. What does tsc report?
3.
Why does a .d.ts file with a declare module block do nothing when the folder is not listed in include?
4.
You write declare global in a file, and the compiler refuses it. What is missing?
5.
You augment an interface from another package and add a required property, debug. What is likely to happen?
About
Five scenario questions on declaration files, ambient modules and augmentation. If you miss more than one, reread the lessons in this section.
- Duration
- 5 min
- Last update
- 10/03/2026
Was this helpful?
0
0
Comments (0)
Sign in to commentNo comments yet.