DefinitelyTyped and @types packages in Typescript - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output when using a missing @types package?

Consider this TypeScript code that imports a library without an installed @types package. What will the TypeScript compiler report?

Typescript

import _ from 'lodash';

const result = _.chunk([1, 2, 3, 4], 2);
console.log(result);

A Compilation warning only, but code runs fine.

B Compilation error: Cannot find module 'lodash' or its corresponding type declarations.

C Runtime error: '_' is undefined.

D No compilation error; the code compiles and runs, but TypeScript treats '_' as 'any' type.

💡 Hint

Think about what happens if TypeScript has no type info but the package is installed.

If the @types/lodash package is missing but lodash is installed, TypeScript treats the import as having type any. This means no compile error, but you lose type safety.

🧠 Conceptual

intermediate

Why use the DefinitelyTyped repository?

What is the main purpose of the DefinitelyTyped repository in the TypeScript ecosystem?

A To host community-maintained type definitions for JavaScript libraries that lack built-in TypeScript types.

B To compile TypeScript code into JavaScript automatically.

C To provide official runtime implementations of popular JavaScript libraries.

D To manage package versions for npm.

💡 Hint

Think about what type definitions are and who maintains them when libraries don't provide their own.

DefinitelyTyped is a community repository that hosts type definition files (.d.ts) for JavaScript libraries that do not include their own TypeScript types.

🔧 Debug

advanced

Identify the error caused by missing @types package

Given this TypeScript code snippet, what error will the compiler show if @types/express is not installed?

Typescript

import express from 'express';

const app = express();
app.get('/', (req, res) => {
  res.send('Hello World');
});

A Error: Cannot find module 'express' or its corresponding type declarations.

B Error: Property 'get' does not exist on type 'any'.

C No error; code compiles and runs fine.

D Error: Cannot find name 'express'.

💡 Hint

Consider what happens when the type declarations for a module are missing.

If @types/express is missing, TypeScript cannot find type declarations for the 'express' module and throws an error about missing module or types.

📝 Syntax

advanced

Which import syntax correctly uses @types package types?

Assuming @types/moment is installed, which import statement correctly imports the moment library with types?

A import { moment } from 'moment';

B import * as moment from 'moment';

C const moment = require('moment');

D import moment from 'moment';

💡 Hint

Check the recommended import style for ES modules with default export.

The @types/moment package defines the module as a namespace export, so import * as moment from 'moment'; is the correct syntax.

🚀 Application

expert

How to add types for a JavaScript library without existing @types package?

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

A Use <code>declare module 'foo-lib';</code> in a global .ts file without any type details.

B Ignore type errors and use <code>any</code> type everywhere for <code>foo-lib</code> imports.

C Create a <code>foo-lib.d.ts</code> file with minimal type declarations and include it in your project.

D Fork DefinitelyTyped and submit a pull request with full type definitions before using the library.

💡 Hint

Think about a practical way to get some type safety quickly.

Creating a local declaration file with minimal types lets you get type safety without waiting for community types. Using just declare module without details loses safety. Forking DefinitelyTyped is good but takes time.