DEV Community

Cover image for πŸ” Skipping Iterations in JavaScript Loops: `for`, `forEach`, and Beyond
Abhinav
Abhinav

Posted on

πŸ” Skipping Iterations in JavaScript Loops: `for`, `forEach`, and Beyond

When working with loops in JavaScript, it's common to want to skip certain iterations β€” whether to avoid processing specific values or just to make the logic cleaner.

But not all loop types work the same way when it comes to skipping!

In this blog, we’ll explore:

  • βœ… How to skip iterations using for loops
  • ❌ Why continue doesn’t work in forEach
  • πŸ’‘ Workarounds and alternatives
  • 🧠 Which loop to choose based on your use case

πŸ§ͺ 1. Skipping Iterations in a for Loop (The Classic Way)

The continue statement is your friend here.

for (let i = 0; i < 5; i++) { if (i === 2) { continue; // Skip when i is 2 } console.log(i); } 
Enter fullscreen mode Exit fullscreen mode

🧾 Output:

0 1 3 4 
Enter fullscreen mode Exit fullscreen mode

βœ… Why it works:

The continue statement tells the loop to skip the rest of the current iteration and move to the next one.


🚫 2. Why continue Doesn’t Work in forEach

[1, 2, 3].forEach((num) => { if (num === 2) { continue; // ❌ SyntaxError! } console.log(num); }); 
Enter fullscreen mode Exit fullscreen mode

Image description
That’s because forEach uses a callback function, and continue is only allowed inside actual loop constructs like for, while, or for...of.


βœ… 3. Skipping in forEach with return

Instead of continue, you can use return to skip the current callback execution:

[1, 2, 3, 4].forEach((num) => { if (num === 3) return; // Skip 3 console.log(num); }); 
Enter fullscreen mode Exit fullscreen mode

🧾 Output:

1 2 4 
Enter fullscreen mode Exit fullscreen mode

snippet-forEach

βœ… Why it works:

Using return exits the current callback function early β€” effectively skipping that iteration.


πŸ” 4. for...of β€” The Flexible Alternative

Need more control (like both continue and break)? for...of is a great middle ground:

const nums = [10, 20, 30, 40]; for (const num of nums) { if (num === 30) continue; console.log(num); } 
Enter fullscreen mode Exit fullscreen mode

🧾 Output:

10 20 40 
Enter fullscreen mode Exit fullscreen mode

You can also use break here if needed β€” which you can’t do with forEach.


🧠 Which Loop Should You Use?

Use Case Best Loop
Need break or continue? for, for...of
Just iterating over items? forEach (if no need to skip/break)
Transforming data? map, filter, reduce
Working with async code? for...of with await

πŸ“Œ Final Thoughts

Choosing the right loop isn’t just about preference β€” it’s about control. If you need to skip, short-circuit, or break, prefer for or for...of. Use forEach only when you're sure you'll process every item and don’t need to interrupt the flow.


✍️ Hope this helped clarify one of those subtle gotchas in JavaScript loops!

Top comments (3)

Collapse
 
vanshul22 profile image
Vanshul Kesharwani

Great post Abhinav!
Just to add - for...in is another option

It iterates over object keys (or array indices),
You can use both break and continue with for...in loop.

Best used for objects:

`
const obj = {a: 1, b: 2, c: 3, d: 4};

for (const key in obj) {
if (key === 'b') continue; // Skip this iteration
if (key === 'd') break; // Exit the loop
console.log(key, obj[key]);
}
// Output: a 1, c 3
`

So for...in has the same flow control as regular for and for...of loops - unlike forEach which can't use break/continue.

Collapse
 
itxitpro_llc profile image
ITXITPro LLC

Great breakdown of loop control in JavaScript! πŸ™Œ I especially liked how you covered the differences between forEach, for...of, and for loops when it comes to skipping iterations. The workaround using return in forEach is a handy reminder, though it definitely makes me appreciate the flexibility of for and for...of more. Thanks for sharing thisβ€”super useful for both beginners and seasoned devs brushing up on fundamentals! πŸ”πŸ’‘

Collapse
 
nevodavid profile image
Nevo David

pretty cool seeing these differences all laid out tbh, you think picking the wrong loop messes up your code long-term or am i just overthinking it

Some comments may only be visible to logged-in visitors. Sign in to view all comments.