Triple-slash directives in Typescript - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a triple-slash directive in TypeScript?

A triple-slash directive is a single-line comment starting with /// that provides compiler instructions, like referencing other files or types.

beginner

How do you reference another file using a triple-slash directive?

You use /// <reference path="filename.ts" /> at the top of your TypeScript file to tell the compiler to include that file.

intermediate

What is the purpose of /// <reference types="..." /> directive?

It tells the compiler to include type declarations from a package, usually from node_modules/@types, so you get type info for libraries.

beginner

Where should triple-slash directives be placed in a TypeScript file?

They must be placed at the very top of the file, before any other code or import statements.

intermediate

Can triple-slash directives affect module resolution in TypeScript?

Yes, they can guide the compiler to find files or types that are not automatically discovered, helping with module resolution.

What does the triple-slash directive /// <reference path="utils.ts" /> do?

A Comments out the utils.ts file

B Imports a module named utils

C Declares a variable named utils

D Includes the file utils.ts for compilation

The directive tells the compiler to include the referenced file utils.ts during compilation.

Where must triple-slash directives appear in a TypeScript file?

A At the very top before any code

B At the bottom of the file

C Anywhere in the file

D Inside functions only

Triple-slash directives must be at the top of the file before any other code or imports.

Which triple-slash directive is used to include type declarations from a package?

A /// <reference path="..." />

B /// <include types="..." />

C /// <reference types="..." />

D /// <import types="..." />

The /// <reference types="..." /> directive includes type declarations from packages.

What symbol starts a triple-slash directive in TypeScript?

A //

B ///

C /*

D <!--

Triple-slash directives start with three slashes: ///.

Can triple-slash directives be used to affect module resolution?

A Yes, they help the compiler find files or types

B No, they only add comments

C Yes, but only for JavaScript files

D No, they are deprecated

Triple-slash directives guide the compiler to find files or types, affecting module resolution.

Explain what triple-slash directives are and how they are used in TypeScript.

Think about how TypeScript knows about other files or type info.

Describe the difference between /// <reference path="..." /> and /// <reference types="..." /> directives.

One is for files, the other is for type packages.

Practice

1. What is the main purpose of /// <reference> triple-slash directives in TypeScript?

easy

A. To import external JavaScript libraries at runtime

B. To add comments visible in the final JavaScript output

C. To define variables globally across files

D. To provide compiler instructions about file dependencies and types

Solution

1. Step 1: Understand triple-slash directive role

   Triple-slash directives are special comments that give instructions to the TypeScript compiler, mainly about type information and file dependencies.

2. Step 2: Identify correct purpose

   They do not affect runtime or add global variables but help the compiler understand relationships between files.

3. Final Answer:

   To provide compiler instructions about file dependencies and types -> Option D

4. Quick Check:

   Triple-slash directives = compiler instructions [OK]

Hint: Triple-slash directives guide the compiler, not runtime code [OK]

Common Mistakes:

• Thinking they add runtime imports
• Confusing with normal comments
• Assuming they define global variables

2. Which of the following is the correct syntax for a triple-slash reference directive in TypeScript?

easy

A. ///

B. //

C. /* */

D.

Solution

1. Step 1: Recall triple-slash directive syntax

   The correct syntax starts with three slashes followed by a space and then the XML-like tag with attributes.

2. Step 2: Match correct option

   /// matches the exact syntax: /// <reference path="..." />. Others miss slashes or use wrong comment style.

3. Final Answer:

   /// <reference path="./types.d.ts" /> -> Option A

4. Quick Check:

   Triple-slash directive syntax = /// <reference ... /> [OK]

Hint: Triple-slash directives always start with exactly three slashes [OK]

Common Mistakes:

• Using two slashes instead of three
• Using block comments instead of triple-slash
• Omitting the closing slash in the tag

3. Given these two TypeScript files:

// file: types.d.ts interface User { name: string; age: number; } // file: app.ts /// <reference path="./types.d.ts" /> const user: User = { name: "Alice", age: 30 }; console.log(user.name);

What will be the output when compiling and running app.ts?

medium

A. undefined

B. Alice

C. Compilation error: User not found

D. Runtime error

Solution

1. Step 1: Understand reference directive effect

   The triple-slash directive includes the type definitions from types.d.ts, so the User interface is known in app.ts.

2. Step 2: Check code behavior

   The object user matches the User interface and logs user.name, which is "Alice".

3. Final Answer:

   Alice -> Option B

4. Quick Check:

   Reference directive allows type use = "Alice" output [OK]

Hint: Reference directives enable type info, so code compiles and runs [OK]

Common Mistakes:

• Assuming missing import causes error
• Confusing type-only files with runtime code
• Expecting runtime errors from type declarations

4. Consider this TypeScript file snippet:

/// <reference path="./types.d.ts" /> const user: User = { name: "Bob", age: 25 }; /// <reference path="./extra.d.ts" /> console.log(user.age);

What is the problem with this code?

medium

A. Triple-slash directives must be at the very top before any code

B. You cannot use multiple triple-slash directives in one file

C. The User type is not defined in any referenced file

D. Console.log cannot be used after triple-slash directives

Solution

1. Step 1: Recall triple-slash directive placement rules

   Triple-slash directives must appear at the very top of the file, before any other code or statements.

2. Step 2: Identify violation in code

   Here, the second triple-slash directive appears after a variable declaration, which is invalid and causes a compiler error.

3. Final Answer:

   Triple-slash directives must be at the very top before any code -> Option A

4. Quick Check:

   Triple-slash directives = top of file only [OK]

Hint: Always place all triple-slash directives before any code [OK]

Common Mistakes:

• Placing directives after code lines
• Thinking multiple directives are disallowed
• Confusing runtime code with compiler instructions

5. You have three TypeScript files:

// types.d.ts interface Config { url: string; timeout: number; } // settings.d.ts /// <reference path="./types.d.ts" /> declare const config: Config; // app.ts /// <reference path="./settings.d.ts" /> console.log(config.url);

What is the correct way to ensure app.ts compiles without errors and recognizes config and Config types?

hard

A. Declare config and Config again inside app.ts

B. Add a triple-slash directive in app.ts referencing both settings.d.ts and types.d.ts

C. Place all triple-slash directives at the top of app.ts referencing settings.d.ts only

D. Remove all triple-slash directives and import modules instead

Solution

1. Step 1: Understand reference chaining

   Since settings.d.ts references types.d.ts, app.ts only needs to reference settings.d.ts to access both Config and config.

2. Step 2: Confirm directive placement

   All triple-slash directives must be at the top of app.ts before any code to work correctly.

3. Final Answer:

   Place all triple-slash directives at the top of app.ts referencing settings.d.ts only -> Option C

4. Quick Check:

   Reference chaining means one directive suffices [OK]

Hint: Reference chaining means only top-level file needs directive [OK]

Common Mistakes:

• Adding redundant references
• Placing directives after code
• Re-declaring types unnecessarily