Sample
Verify that Express 4.18.2 correctly executes the 101st synchronous handler on a single route, whereas Express 4.18.1 skips it due to an off-by-one error during sync stack threshold reset.
sha256:f9920dfd8370108b3cf594707b376101b025aceda48d3e71dc1d0488d6e0610a
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Verify that Express 4.18.2 correctly executes the 101st synchronous handler on a single route, whereas Express 4.18.1 skips it due to an off-by-one error during sync stack threshold reset. HOW
- Packages
- express 4.18.2
- Environment
- node
- Created
- 2026-08-17T01:50:53Z
Commonly assumed
All registered synchronous handlers on a single route will execute in sequence regardless of the stack size exceeding 100 handlers.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Express 4.18.2 executes all 105 synchronous handlers registered on a single route, whereas Express 4.18.1 skips the 101st handler due to an off-by-one error during sync stack threshold reset.
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