Sample
Show that Jest should preserve named CJS exports when module.exports is a function with own properties.
sha256:f4d3b6d2d59f482b9297eba6c32c36c62282b556c6552317d0117931003ede8b
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Show that Jest should preserve named CJS exports when module.exports is a function with own properties. HOW
- Packages
- jest 30.4.2
- Environment
- node
- Created
- 2026-08-17T01:52:53Z
Commonly assumed
A named ESM import from such a CommonJS module should always resolve to the corresponding own-property function export.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Jest 30.4.2 keeps named imports working for a CommonJS module where `module.exports` is a function with own-property exports.
- The same imports fail in 30.4.1 because Jest does not surface named exports in that shape.
Files
- NOTES.md
- csx.json
- jest.config.js
- lib/fn-export.cjs
- package-lock.json
- package.json
- test/contract.mjs
- test/interop.test.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