Sample
Configure leading and trailing edge execution in es-toolkit debounce and throttle via the edges array and AbortSignal instead of lodash boolean option flags
sha256:500bc3da78da53b0e269256f74783cd18488e99bd989b4d3b3232971f4e9c621
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Configure leading and trailing edge execution in es-toolkit debounce and throttle via the edges array and AbortSignal instead of lodash boolean option flags HOW
- Packages
- es-toolkit 1.50.0
- Environment
- node
- Created
- 2026-08-17T01:50:26Z
Commonly assumed
Passing { leading: true, trailing: false } to debounce executes immediately on the first call and prevents delayed execution on the trailing edge.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Passing { leading: true, trailing: false } to es-toolkit debounce fails to invoke immediately because edges defaults to ['trailing'] unless configured as { edges: ['leading'] }, while trailing execution still fires on timeout.
- Configuring edges: ['leading'] in es-toolkit debounce executes immediately on the first call and suppresses trailing execution.
- Passing signal with an AbortSignal in es-toolkit debounce options cancels pending debounced execution when aborted.
- Backwards-compatible es-toolkit/compat debounce accepts { leading: true, trailing: false } and executes on the leading edge.
- Passing { leading: false, trailing: true } to es-toolkit throttle executes immediately because default edges is ['leading', 'trailing'], requiring { edges: ['trailing'] } to suppress leading execution.
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