JavaScript Math.max RangeError on Large Arrays: Scan the Values
Reproduce the Math.max RangeError with spread and apply on a large array, then verify a scan that preserves NaN and signed zero behavior.
Reproduce the Math.max RangeError with spread and apply on a large array, then verify a scan that preserves NaN and signed zero behavior.
Trace where URLSearchParams loses a literal plus sign. Compare raw queries, set(), and pre-encoded inputs with round-trip checks for +, spaces, and %2B.
See why Promise.finally can hide a rejected operation when cleanup fails, then run six Node.js checks for a wrapper that preserves both rejection reasons.
See why isNaN accepts blank strings, then test a form parser that keeps zero and rejects blank or non-finite amounts before they reach a JSON payload.
See how toSorted and spread change sparse array holes into undefined, then verify that slice().sort() preserves the hole count and leaves the source intact.
Prove that a Promise.race timeout leaves work running, then compare result selection with abortable Node.js timers and explicit cleanup ownership.
Trace numeric key ordering, leading zeros, and the array-index limit with executable checks. Preserve insertion order with Map or JSON entry arrays.
Fix required-list validation with a runnable every() matrix covering empty arrays, sparse slots, and inherited entries, plus an explicit own-entry guard.