break Statement
Learn break Statement
break exits the nearest enclosing loop or switch immediately.
In this lesson, you will study the rule, run a complete TypeScript example, explain its output, and test a small change.
What you’ll learn
- Explain the main rule behind break statement.
- Predict the result of the complete runnable TypeScript example.
- Recognize one common mistake and correct it.
Understand the concept
It is useful after finding the first matching item or deciding that more iterations are unnecessary. Statements after break inside the same body are not executed. In nested loops, an unlabeled break exits only the inner loop.
See the concept visually
Use the diagram to locate the checks, values or branches involved in the example.
Run a complete TypeScript example
Save this code as main.ts or paste it into the TypeScript Playground. The example uses fixed values so it runs without prompting for input.
TypeScript code
for (let id = 1; id <= 5; id++) {
if (id === 3) {
break;
}
console.log(id);
}
console.log("Stopped");Verified output
1
2
StoppedHow to run locally: npx tsc --strict --target es2022 --module commonjs main.ts, then node main.js. When using a project configuration, run the matching project build instead.
Trace the execution
Values 1 and 2 are printed. When id becomes 3 the condition succeeds and break ends the loop; the final message then prints.
Predict the output before you run the sample. Compare each line with the source expression that produced it, and distinguish the type checker’s work from what happens in JavaScript at runtime.
Common mistakes and how to avoid them
break exits a loop; continue skips only one iteration. Do not use them interchangeably.
Debugging habit: when a change is rejected, read the exact compiler diagnostic and inspect the operand types. When it compiles but behaves unexpectedly, follow the values through the JavaScript expressions.
Practice it yourself
Change the break condition to id === 5. Predict the values printed, then try a nested loop and observe what exits.
Challenge: write down your prediction first, run the changed source, and explain any difference. Return to the verified version before continuing.
Check your understanding
Review the key idea
break Statement: It is useful after finding the first matching item or deciding that more iterations are unnecessary.
break transfers control to the statement after the loop.
Before continuing, be able to explain what is checked before execution and what actually changes at runtime in the example above.
Reaching the recap and completing the quizzes are separate milestones.