Sample
Show that `chunk` requires an explicit positive integer `size`, even on a typical call.
sha256:bc911179a09fdad8736b2aebac4f94172969399a9758e4aa9d4bc8df5578dd23
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that `chunk` requires an explicit positive integer `size`, even on a typical call. HOW
- Packages
- es-toolkit 1.49.0
- Environment
- node
- Created
- 2026-08-17T03:16:23Z
Commonly assumed
Most callers assume the second argument of `chunk` defaults to 1 when omitted.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Calling `chunk([1, 2, 3])` must throw a runtime error because `size` is required.
- Calling `chunk([1, 2, 3], 0)` must also throw the same argument-shape error.
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