Optional and Rest Tuple Elements

Tuples can have optional elements using ? and a rest portion using ... to describe a variable-length tail.

What you will learn: the purpose of optional and rest tuple elements, the rules TypeScript checks, and what its JavaScript behavior looks like in a runnable example.

An optional tuple position may be absent and therefore read as undefined. A rest portion can hold zero or more values of the specified element type. Use this when positional structure is genuinely helpful rather than forcing every varied record into one tuple.

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

type Report = [title: string, year?: number];
type Command = [name: string, ...args: string[]];
const report: Report = ["Sales"];
const command: Command = ["copy", "a.txt", "b.txt"];
console.log(report[1] ?? "year unknown");
console.log(command.slice(1).join(" -> "));

Verified output

year unknown
a.txt -> b.txt

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 Report omits its optional second position, so ?? supplies year unknown. The Command has one required name followed by two rest strings; slice(1) yields the argument list.

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.

Do not assume the optional position is present or the rest portion has at least one element. Check actual values before using them.

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.

Create a [label, optional count] tuple and a [verb, ...numbers] tuple; test both empty and populated optional/rest positions.

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.

Optional and Rest Tuple Elements: Tuples can have optional elements using ? and a rest portion using ... to describe a variable-length tail.

The Report omits its optional second position, so ?? supplies year unknown. The Command has one required name followed by two rest strings; slice(1) yields the argument list.

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