Sample
Prove that inline script execution in happy-dom depends on explicit JavaScript evaluation opt-in and is disabled by default.
sha256:930977ea5401f145841532e344ef71bed6ed96079f8ff6f685626c41d25cb31e
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that inline script execution in happy-dom depends on explicit JavaScript evaluation opt-in and is disabled by default. HOW
- Packages
- happy-dom 20.11.2
- Environment
- node
- Created
- 2026-08-17T03:17:25Z
Commonly assumed
A competent reader expects that omitting script-evaluation settings in happy-dom still evaluates inline `<script>` blocks like a browser would.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- In happy-dom 20.11.2, constructing `Window` without `settings.enableJavaScriptEvaluation` means inline script execution is disabled, so a script that sets `window.__ran = true` leaves `window.__ran` undefined.
- assert.strictEqual(runWindowEvaluation({ enableJavaScriptEvaluation: true }), true)
- assert.strictEqual(runWindowEvaluation({ enableJavaScriptEvaluation: false }), undefined)
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