- 01Setting Up (What You'll Need)
- 02Creating Variables
- 03Conditionals (if Statements)
- 04Loops (for Statements)
- 05Creating Functions
- 06Working with Arrays
- 07Working with Objects
- 08Loops (while Statements)
- 09Working with Strings
- 10Using Classes (Object-Oriented Programming)
- 11Error Handling (try...catch)
- 12Destructuring and the Spread Syntax
- 13Async Code (Promise / async & await)
- 14Advanced Array Methods (filter and reduce)
- 15The switch Statement
- 16The Ternary Operator
- 17Inheritance (Extending Classes)
- 18How to Write Comments
- 19Logical Operators (AND, OR, NOT)
- 20Constants (Making Read-Only Values with const)
- 21Splitting and Joining Strings (split and join)
- 22Null-Safe Syntax (?? and ?.)
- 23Searching Arrays and Collections (includes and find)
- 24Transforming Arrays with map
- 25Two-Dimensional Arrays (Table-Shaped Data)
- 26Building a Custom Error Class
- 27Default Arguments (Setting Initial Values for Parameters)
- 28Using Set (Collections)
- 29Verifying Correctness with assert (Your First Step Into Testing)
- 30Higher-Order Functions (Passing a Function as an Argument)
- 31Stacks and Queues (Basic Data Structures)
- 32The Basics of Type Conversion (Casting)
- 33Introduction to Regular Expressions (Pattern Matching)
- 34The Binary Search Algorithm
- 35Building a Caesar Cipher (a Letter-Shifting Cipher)
- 36Understanding How Bubble Sort Works
- 37Building and Displaying Dates (Basic Year/Month/Day Operations)
- 38Writing Several Unit Tests Together (Multiple Test Cases)
- 39Speeding Up Calculations with Memoization (Caching)
- 40Normalizing Strings (trim and Case Unification)
- 41The Difference Between Shallow Copy and Deep Copy
- 42The Basics of Enums (Enumerated Types)
- 43Flattening Arrays (flatten)
- 44Reversing a String and Checking for a Palindrome
- 45Pairing Up Two Arrays (a zip Operation)
- 46Rounding Numbers (floor, ceil, and round)
- 47Multi-Line Strings (Template Literals)
- 48Returning Multiple Values from a Function (Array Destructuring)
- 49Finding the GCD and LCM (the Euclidean Algorithm)
- 50Formatting Numbers (Digit Alignment and Decimal Precision)
- 51Cleanup Processing with try/catch/finally
- 52Writing Type-Agnostic, General-Purpose Functions
- 53The Basics of Map (an Object for Key-Value Pairs)
- 54Generating Random Numbers
- 55Bitwise Operations (AND, OR, XOR, and Shift Operations)
- 56Using static (Static Class Properties and Methods)
- 57Waiting a Fixed Amount of Time (setTimeout and await)
- 58Watch Out for Floating-Point Rounding Error
- 59Transforming and Flattening at Once with flatMap()
- 60FizzBuzz (the Classic Practice Problem)
- 61Checking Whether a Number Is Prime
- 62Set Operations with Set (Union, Intersection, and Difference)
- 63Converting Number Bases (Binary and Hexadecimal)
- 64Checking That Brackets Match (an Application of Stacks)
- 65Checking for an Anagram
- 66Checking Whether a Year Is a Leap Year
- 67Converting Temperature (Celsius ⇄ Fahrenheit)
- 68Finding the Prime Factorization
- 69[Applied] Build a Simple To-Do List Tool
The switch Statement
In this lesson you'll learn how to write a switch statement in JavaScript so you can express branching on a single value more clearly than a chain of if statements. This is for people searching "JavaScript switch statement usage" or "JavaScript switch break."
A switch statement is a way to branch on a single value that's often easier to read than lining up if / else if. It's written as switch (value) { case value1: ...; break; ... default: ...; }, and the processing under whichever case matches gets executed. It's commonly used for things like picking a day of the week or choosing a menu option — deciding among a fixed set of choices.
The sample code displays a day name based on the value of the day variable. It matches case 3:, so "Wednesday" is displayed, and then break exits the switch statement. If none of the cases match, the default block runs — this plays the same role as an if statement's else.
The single most common beginner mistake is forgetting to write break. Without break, execution "falls through" from the matched case straight into the processing of the next case too. This tends to cause bugs, but it's also sometimes deliberately used when you want several cases to share the same processing — a somewhat special quirk of the language.
In real development, switch statements are commonly used to switch what's displayed or how something is processed based on a status — an order's state, or a permission level, for example. When there are three or more branch options and you can decide based on a single value, a switch statement usually communicates intent more clearly than a chain of if/else ifs.
If you want several cases to run the same processing, you can write case 1: and case 2: back to back with no code in between, letting both values run the same block (deliberately using fall-through).
You can also use strings as the value in a switch statement. Writing something like case "Monday": lets you branch on strings just as easily as numbers — a pattern often used for things like dispatching on the type of a command in real projects.
💡 Anything passed to console.log() appears in the output below.
