What do Array.some and Array.every do?

Q: What do Array.some and Array.every do?

**Target Audience:** Engineers preparing for JavaScript array-method interviews. **Difficulty:** Easy > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . The real call-counter proof and the real empty-array edge cases below were **actually run** — not descriptions of documented behavior. ## 1. Why This Even Matters — A Story First A security guard checking IDs at a door who genuinely stops the moment they spot ONE underage person, rather than continuing to check everyone else in line first — some() behaves exactly like that guard, verified directly below with a real, counted proof it genuinely does not keep going once it already has its answer. ## 2. The Core Idea 📌 **Interview term:** `some()` answers "does **at least one** pass"; `every()` answers "do **all** pass" — both genuinely **short-circuit**, stopping the instant the real answer is already determined. Verified directly below with a real call count

The problem

Question presented to candidate: "You have an array of 1000 users, and you want to check if any of them are under 18. Would some() actually stop checking once it finds one, or does it genuinely check all 1000 regardless? Same question for every() — checking that all users are adults."

What a strong answer should cover:

📌 Interview term: some(predicate) — returns true if at least one element genuinely passes the predicate; 📌 every(predicate)** — returns true only if all elements genuinely pass.
📌 Verified, not assumed — directly answering the prompt's exact question: a real call counter proved both methods genuinely short-circuit — some() genuinely stopped calling its predicate at exactly the element that first returned true (not continuing through the rest of the array), and every() genuinely stopped at exactly the element that first returned false.
📌 Interview term: the real, vacuous-truth edge cases — confirmed directly: an empty array's some() genuinely returns false (no element exists to pass), while an empty array's every() genuinely returns true (there is no element to fail the check) — a real, easy-to-get-backwards pair of facts, worth memorizing precisely rather than guessing.
A precise answer names some/every as answering genuinely existential ("does at least one exist") versus universal ("do all satisfy") questions about an array — the real, direct vocabulary an interviewer expects.
The precise, honest scope: both methods genuinely only report a boolean — if the actual, specific matching element itself is needed (not just whether one exists), find() (covered in this bank's own dedicated question) is the correct, more direct tool.

Clarifying questions expected:

"Does the actual downstream code need the specific matching element itself, or just a yes/no answer to whether one exists?" — directly decides between some/every (verified above as boolean-only) and find (covered in this bank's own dedicated question).
"Is the actual predicate function genuinely expensive to run per element?" — the real short-circuiting verified above is specifically valuable when each individual check has a real, meaningful cost.

Code / implementation expected: Yes — a real call counter directly proving both methods genuinely stop early, plus the real empty-array vacuous-truth outcomes, is the concrete, convincing proof of exactly how efficiently — and correctly — these two methods behave.

some
every

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for JavaScript array-method interviews. Difficulty: Easy

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. The real call-counter proof and the real empty-array edge cases below were actually run — not descriptions of documented behavior.

1. Why This Even Matters — A Story First

A security guard checking IDs at a door who genuinely stops the moment they spot ONE underage person, rather than continuing to check everyone else in line first — some() behaves exactly like that guard, verified directly below with a real, counted proof it genuinely does not keep going once it already has its answer.

2. The Core Idea

📌 Interview term: some() answers "does at least one pass"; every() answers "do all pass" — both genuinely short-circuit, stopping the instan

The solution is hidden so you can try first

6 min read · 8 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.

JavaScriptReal proof: a call counter confirms both some() and every() genuinely short-circuit, plus the real empty-array vacuous-truth outcomes