DefinitelyTyped and @types packages in Typescript - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to install type definitions for a package using npm.

Typescript

npm install --save-dev [1]

Drag options to blanks, or click blank then click option'

Alodash

B@types/lodash

Ctypescript

D@types/node

Attempts:

3 left

💡 Hint

Common Mistakes

Installing the main package instead of the '@types' package.

Forgetting to add '--save-dev' for development dependencies.

To add type definitions for a package like lodash, you install the corresponding @types package.

2fill in blank

medium

Complete the code to import a type from an installed '@types' package.

Typescript

import type { [1] } from 'lodash';

Drag options to blanks, or click blank then click option'

Amap

BmapFn

CMap

DMapper

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase names for types.

Importing values instead of types with 'import type'.

The type Map is a valid type exported by lodash's type definitions.

3fill in blank

hard

Fix the error in the code by completing the import statement for a type from '@types/node'.

Typescript

import type { [1] } from 'node';

Drag options to blanks, or click blank then click option'

ABuffer

Bbuffer

CBufferType

DBufferClass

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'buffer' which is not a type.

Guessing type names that don't exist.

The correct type to import from '@types/node' is Buffer with uppercase B.

4fill in blank

hard

Fill both blanks to create a type alias for a function type using types from '@types/lodash'.

Typescript

type Func = (input: string) => [1];

const example: Func = (input) => [2];

Drag options to blanks, or click blank then click option'

Anumber

Binput.length

Cstring

Dinput.toUpperCase()

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'string' as return type but returning a number.

Returning a string when the type expects a number.

The function returns a number, so the type is number and the example returns the length of the input string.

5fill in blank

hard

Fill all three blanks to create a typed object using types from '@types/node' and '@types/lodash'.

Typescript

import type { [1] } from 'node';
import type { [2] } from 'lodash';

const data: { buf: [1]; fn: [2] } = {
  buf: Buffer.from('hello'),
  fn: (arr) => arr.map(x => x * 2)
};

Drag options to blanks, or click blank then click option'

ABuffer

Bmap

CMap

DFunction

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing function names with types.

Using lowercase names for types.

The type Buffer is imported from 'node' and Map is a type from 'lodash'. The object uses these types for its properties.

Practice

1. What is the main purpose of the @types packages in TypeScript?

easy

A. To provide type definitions for JavaScript libraries

B. To compile TypeScript code into JavaScript

C. To run JavaScript code in the browser

D. To create new JavaScript libraries

Solution

1. Step 1: Understand the role of @types packages

   @types packages contain type definitions that describe the shape and types of JavaScript libraries for TypeScript.

2. Step 2: Identify the main purpose

   They help TypeScript understand JavaScript libraries by providing type information, enabling better type checking and editor support.

3. Final Answer:

   To provide type definitions for JavaScript libraries -> Option A

4. Quick Check:

   @types = type definitions [OK]

Hint: Remember: @types adds types for JS libs [OK]

Common Mistakes:

• Confusing @types with compilers
• Thinking @types runs code
• Assuming @types creates libraries

2. Which of the following is the correct way to install type definitions for the lodash library using npm?

easy

A. npm install @types/lodash

B. npm install lodash-types

C. npm install types-lodash

D. npm install lodash/@types

Solution

1. Step 1: Recall the naming convention for type packages

   Type definitions from DefinitelyTyped are published under the @types scope, so the package name is @types/library-name.

2. Step 2: Match the correct npm install command

   For lodash, the correct package is @types/lodash, so the command is npm install @types/lodash.

3. Final Answer:

   npm install @types/lodash -> Option A

4. Quick Check:

   Type packages start with @types/ [OK]

Hint: Type packages always start with @types/ [OK]

Common Mistakes:

• Using incorrect package names without @types/
• Mixing up package and type package names
• Trying to install types as normal packages

3. Given the following TypeScript code, what will be the output if @types/lodash is NOT installed?

import _ from 'lodash';

const numbers = [1, 2, 3];
const doubled = _.map(numbers, n => n * 2);
console.log(doubled);

medium

A. [] (empty array)

B. [2, 4, 6]

C. Runtime error: _.map is not a function

D. TypeScript error: Cannot find module 'lodash' or its corresponding type declarations

Solution

1. Step 1: Understand the role of type definitions in TypeScript

   Without @types/lodash, TypeScript cannot find type information for lodash, causing a compile-time error.

2. Step 2: Identify the error message

   The error will say it cannot find the module or its type declarations, preventing compilation.

3. Final Answer:

   TypeScript error: Cannot find module 'lodash' or its corresponding type declarations -> Option D

4. Quick Check:

   No types = compile error [OK]

Hint: No @types means TypeScript can't find types [OK]

Common Mistakes:

• Confusing runtime errors with compile errors
• Expecting code to run without types installed
• Thinking JavaScript errors appear instead

4. You installed @types/express but still get errors about missing types when importing express. What is the most likely cause?

medium

A. You need to restart your TypeScript server or IDE

B. You installed the wrong version of @types/express

C. You forgot to install the express package itself

D. You must import types explicitly using import type

Solution

1. Step 1: Check dependencies

   Type definitions only provide types; the actual library must be installed separately.

2. Step 2: Identify missing library

   If express is not installed, importing it causes errors despite having types.

3. Final Answer:

   You forgot to install the express package itself -> Option C

4. Quick Check:

   Types need actual library installed [OK]

Hint: Always install both library and its @types [OK]

Common Mistakes:

• Assuming types include the library code
• Not restarting IDE after install
• Misusing import type for libraries

5. You want to use a JavaScript library foo-lib in your TypeScript project, but no @types/foo-lib package exists. What is the best way to add type support?

hard

A. Ignore type errors and use any everywhere

B. Write a custom declaration file foo-lib.d.ts with needed types

C. Install @types/foo-lib anyway, it will work

D. Rewrite the library in TypeScript

Solution

1. Step 1: Understand missing type definitions

   If no official @types package exists, you can create your own declaration file to describe the library's types.

2. Step 2: Choose best practice

   Writing a .d.ts file lets TypeScript check your code and improves editor support without rewriting the library.

3. Final Answer:

   Write a custom declaration file foo-lib.d.ts with needed types -> Option B

4. Quick Check:

   Custom .d.ts files add missing types [OK]

Hint: Create .d.ts files for missing types [OK]

Common Mistakes:

• Ignoring types and risking bugs
• Expecting non-existent @types packages
• Thinking rewriting library is easiest