TypeScript Project Planning & Execution 5

Question 1

Your team wants to enforce that no `any` types are used anywhere in the codebase via CI. Which ESLint rule from `@typescript-eslint` enforces this?

Accepted Answer

@typescript-eslint/no-explicit-any

Answer

`@typescript-eslint/no-explicit-any` flags any usage of the `any` type, encouraging proper typing throughout the codebase.

Question 2

In a TypeScript monorepo with project references, what command rebuilds only packages whose sources changed since the last build?

Accepted Answer

tsc -b

Answer

`tsc -b` (build mode) reads project references and only recompiles packages with changed sources using `.tsbuildinfo` cache files.

Question 3

When adding a new team member to a TypeScript project, which file should they check first to understand the compiler configuration and strictness level?

Accepted Answer

tsconfig.json

Answer

`tsconfig.json` defines the TypeScript compiler options including strictness flags, target environment, and module resolution strategy.

Question 4

Which approach is recommended when a TypeScript project needs to share type definitions between a frontend and backend in a monorepo?

Accepted Answer

Create a shared `types` package referenced by both frontend and backend

Answer

A shared `types` package ensures the frontend and backend agree on data shapes, catching type mismatches at compile time.

Question 5

A developer needs to run TypeScript files directly in Node.js without a compile step during development. Which tool enables this?

Accepted Answer

ts-node or tsx

Answer

`ts-node` (or the faster `tsx`) registers a TypeScript compiler hook in Node.js so `.ts` files execute directly without explicit compilation.

TypeScript Practice Test

TypeScript Practice Test

TypeScript Project Planning & Execution 5