What are declaration files (.d.ts)? | Interview Question

Q: What are declaration files (.d.ts)?

**Target Audience:** Developers who install packages, see "Could not find a declaration file", or need to publish a library with types. **Difficulty:** Medium **TypeScript version:** Every compiler message and output below was produced with TypeScript 5.4.5 (`--strict`, target ES2022). The multi-file projects in sections 3 to 6 were compiled separately with the same compiler, since the page runs a single file. > **How to read this doc:** Each idea is explained in plain language first, then tagged with `📌 Interview term:` so you also learn the exact words an interviewer expects. All output was produced by actually running the code; the **Verified** section quotes it in full. A `.d.ts` file is made of ambient declarations, the subject of [What does the declare keyword do?](/interview-question/what-does-the-declare-keyword-do) Adding to a package's types from the outside is [module augmentation](/interview-question/what-is-module-augmentation). ## 1. Why This Even Matters — A Story Fi

The problem

Question presented to candidate: "What is a .d.ts file? Where do they come from, how does TypeScript find the types for a package you install, and what happens when a declaration file is wrong?"

What a strong answer should cover:

A .d.ts file contains only types (ambient declarations): it describes JavaScript that exists elsewhere and produces no output of its own
Where they come from: generated by tsc --declaration from your own .ts, shipped by a package ("types" in package.json), published to @types/* from DefinitelyTyped, or written by hand (globals, declare module "*.svg")
What happens with none: under strict (noImplicitAny), importing an untyped JavaScript package is error TS7016
Declarations are trusted, not checked against the JavaScript: a wrong .d.ts compiles and crashes at run time
skipLibCheck skips type-checking .d.ts files: faster builds, but a broken declaration then silently degrades to any
Script vs module .d.ts: a file with top-level import/export is a module; global declarations and wildcard declare module patterns belong in a script file (or declare global)

Code / implementation expected: Optional — the .d.ts that tsc --declaration emits for a small module, or a hand-written declaration for an untyped package.

declaration
dts

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Developers who install packages, see "Could not find a declaration file", or need to publish a library with types. Difficulty: Medium TypeScript version: Every compiler message and output below was produced with TypeScript 5.4.5 (--strict, target ES2022). The multi-file projects in sections 3 to 6 were compiled separately with the same compiler, since the page runs a single file.

How to read this doc: Each idea is explained in plain language first, then tagged with 📌 Interview term: so you also learn the exact words an interviewer expects. All output was produced by actually running the code; the Verified section quotes it in full.

A .d.ts file is made of ambient declarations, the subject of What does the declare keyword do? Adding to a package's types from the outside is [module augme

The solution is hidden so you can try first

11 min read · 11 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

TypeScriptA declaration is trusted, not checked

Practice

TypeScriptThe type surface a .d.ts keeps

Practice

Discussion

Other approaches, follow-ups and how it went in real interviews.

Sign in to join the discussion.

No comments yet. Share how you would answer it.

The solution is hidden so you can try first

Keep your momentum going.