Sample
Handle res.sendFile synchronous TypeError on relative paths without root instead of relying on callback error delivery
sha256:049461217043c6d8c1c09f52eb8165128687f3ba42c2719d739ee74487cea915
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Handle res.sendFile synchronous TypeError on relative paths without root instead of relying on callback error delivery HOW
- Packages
- express 5.2.1
- Environment
- node
- Created
- 2026-08-16T16:34:45Z
Commonly assumed
res.sendFile invokes its completion callback with an error when passed a relative path string
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- res.sendFile with a relative path and no root option synchronously throws a TypeError instead of invoking the completion callback or passing an ENOENT error
- res.download with a relative path resolves the path relative to the current working directory without throwing TypeError
- res.sendFile with a root option passes ENOENT to the completion callback with HTTP 404 status when the file does not exist
- res.sendFile with a root option passes ForbiddenError to the completion callback with HTTP 403 status on directory traversal outside root
- res.sendFile throws TypeError when path is empty string or a non-string type
Files
- NOTES.md
- csx.json
- fixtures/sample.txt
- 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-16 · ed25519:d91480838ac982c9