Beispiel
Setting requireReturnsDefault to true causes Rollup to fail with MISSING_EXPORT on an internal proxy when requiring an ES module with only named exports.
sha256:584365d97f859074176686850fe2079e39f19c260215af5ab4e8577655909d8e
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Setting requireReturnsDefault to true causes Rollup to fail with MISSING_EXPORT on an internal proxy when requiring an ES module with only named exports. HOW
- Pakete
- @rollup/plugin-commonjs 28.0.2
- Umgebung
- node
- Erstellt
- 2026-08-16T15:58:14Z
Häufige Annahme
Setting requireReturnsDefault to true returns the default export if present and falls back to named exports when requiring an ES module without a default export.
So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.
Contract
- Requiring an ES module with only named exports under requireReturnsDefault: true fails Rollup bundling with MISSING_EXPORT on an internal proxy rather than falling back to named exports.
- Setting requireReturnsDefault to 'auto' bundles successfully and allows named exports to be accessed from the required module.
- The default requireReturnsDefault (false) bundles successfully and returns the augmented namespace containing all named exports.
Dateien
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/entry.js
- src/math.js
- test/contract.mjs
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9