Building Reusable Generic Utilities

Build generic utilities by identifying a meaningful relationship between the input types, constraints, and output types.

What you will learn: the purpose of building reusable generic utilities, the rules TypeScript checks, and what its JavaScript behavior looks like in a runnable example.

A reusable helper should be small enough to explain and should not use any or unchecked casts when the type system can express the contract. For property access, K extends keyof T and T[K] ensure the selected value retains its type.

Key distinction: TypeScript checks the declared types during development; emitted JavaScript carries out the value-level operation at runtime. A type declaration alone never validates untrusted runtime input.

Read this illustration from the first labeled part to the last. Compare it with the example and identify which parts are type checks and which parts run in JavaScript.

This self-contained example uses fixed values, so it runs without reading input or depending on an external service. Paste it into the TypeScript Playground or save it as main.ts.

TypeScript program

function select<T, K extends keyof T>(item: T, keys: readonly K[]): Pick<T, K> {
  const result = {} as Pick<T, K>;
  for (const key of keys) result[key] = item[key];
  return result;
}
const person = { id: 2, name: "Asha", active: true };
const summary = select(person, ["id", "name"]);
console.log(summary.id);
console.log(summary.name.toUpperCase());

Verified output

2
ASHA

Run locally: npx tsc --strict --target es2022 --module commonjs main.ts, then node main.js. For projects with a tsconfig.json, build using that configuration instead.

The keys array restricts selection to id and name. The loop copies those own readable properties into a new result. TypeScript returns a Pick containing numeric id and string name; the example prints 2 and ASHA.

Check each step: identify the input values, follow the JavaScript operation in execution order, and match the final expression with the exact output shown. An annotation can reject invalid source before execution, but does not change the value printed.

The helper’s internal assertion supports gradually building an object; it is not validation. An external input with missing runtime keys can still break the intended contract.

How to debug: reproduce the issue in a minimal example. For compiler errors, inspect the inferred and declared types; for a runtime surprise, log the actual values and follow their references or branches.

Extend select to pick id and active; then attempt an unknown key and inspect the compile error.

Practice routine: predict the result on paper, edit one part of the code, compile under --strict, run the JavaScript, and explain whether TypeScript caught an error or JavaScript simply behaved differently.

Building Reusable Generic Utilities: Build generic utilities by identifying a meaningful relationship between the input types, constraints, and output types.

The keys array restricts selection to id and name. The loop copies those own readable properties into a new result. TypeScript returns a Pick containing numeric id and string name; the example prints 2 and ASHA.

Before continuing, explain one valid use case, one common pitfall, and the separation between compile-time checking and runtime behavior for this feature.