DEV Community

Why you can't break a forEach loop | ByteSize JS

Jared on March 31, 2020

I recently had a coding interview that involved evaluating one schema against another. The details of it aren't that important, but one thing that ...

Read full post

Folke Lemaitre • Mar 31 '20 • Edited

You can use .every() instead and return false whenever you want to break. Return true to keep going

Jared • Mar 31 '20

Interesting! Thank you for your insight. I haven't used every much. Very handy!

Folke Lemaitre • Mar 31 '20

.some() is probably even better in most cases. Just return true whenever you need to break. No need to return anything when you want to keep going :)

Jared • Mar 31 '20

Sweet! May have to do a deep dive article into all the various loop types.

Usman Khalil • Mar 31 '20

This is so helpful

Jared • Mar 31 '20

Thanks! Any other topics you'd like me to tackle?

Ken Bellows • Apr 1 '20 • Edited

Awesome article! Minor nitpick though: Array.prototype.forEach() and its siblings map, filter, reduce, reduceRight, some, and every were all actually introduced back in 2009 with ES5!

I bring this up not for know-it-all points, but because it's important for browser compatibility. Most of these methods are available in browser versions going back 10+ years, which is super important and helpful if, like me, you work in an environment where you still need to maintain support for those browsers 😭