The switch Statement

When you're comparing one value against a list of specific options, a long chain of else if can get repetitive:

if (day === "Monday") {
  ...
} else if (day === "Tuesday") {
  ...
} else if (day === "Wednesday") {
  ...
}

For this situation, JavaScript has the switch statement:

const day = "Saturday";

switch (day) {
  case "Monday":
    console.log("Ugh. Coffee, please. ☕");
    break;
  case "Friday":
    console.log("Almost the weekend! 🎉");
    break;
  case "Saturday":
  case "Sunday":
    console.log("Weekend! Time to relax. 😎");
    break;
  default:
    console.log("Just another day.");
}

Weekend! Time to relax. 😎

Here's how it works:

• switch (day) says "let's look at the value of day."
• Each case is one possible value to compare against (using strict === comparison).
• When a case matches, JavaScript runs the code under it...
• ...until it hits a break, which jumps out of the whole switch.
• default is like the final else: it runs if no case matched.

Notice how "Saturday" and "Sunday" share the same code? When a case has no code and no break, JavaScript "falls through" to the next case. This lets you group several values together.

const fruit = "apple";

switch (fruit) {
  case "apple":
    console.log("Apples are red.");
  case "banana":
    console.log("Bananas are yellow.");
  case "grape":
    console.log("Grapes are purple.");
}

Apples are red.
Bananas are yellow.
Grapes are purple.

if/else or switch?

Honestly? Lots of developers just use if/else if almost all the time. Both are fine. Use whichever makes your code easier to read.