Sample
Prove that p-limit map’s argument order is iterable-first, not callback-first.
sha256:700635bd470c15e4480d490bad3483a639d29a990016276534d3bf1651a6e366
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that p-limit map’s argument order is iterable-first, not callback-first. HOW
- Packages
- p-limit 7.3.1
- Environment
- node
- Created
- 2026-08-17T03:18:11Z
Commonly assumed
A competent caller expects `limit.map(mapper, iterable)` like `Array.prototype.map`.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- await pLimit(2).map([1, 2, 3], (value) => value * 2) must resolve to [2, 4, 6]
- pLimit(2).map((value) => value * 2, [1, 2, 3]) must throw a TypeError
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9