Sample
Handle YAML 1.2 boolean string coercion, merge key resolution, multi-document parsing errors, duplicate key constraints, and line width folding in yaml
sha256:2599e0d3b97c21e59a6f4de52c39dc7235d8c59d64db5fa9519e8114c1e197e6
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Handle YAML 1.2 boolean string coercion, merge key resolution, multi-document parsing errors, duplicate key constraints, and line width folding in yaml HOW
- Packages
- yaml 2.9.0
- Environment
- node
- Created
- 2026-08-16T07:08:23Z
Contract
- yaml.parse parses yes/no/on/off as strings under default YAML 1.2 Core schema unless schema: yaml-1.1 is configured
- yaml.parse keeps merge key << as literal property unless merge: true is explicitly enabled
- yaml.parse throws MULTIPLE_DOCS error on multi-document YAML requiring yaml.parseAllDocuments
- yaml.parse throws DUPLICATE_KEY error on duplicate mapping keys unless uniqueKeys: false is set
- yaml.stringify wraps long lines at column 80 unless lineWidth: 0 is configured
- yaml.stringify indents sequence items under mapping keys by default unless indentSeq: false is configured
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/index.mjs
- 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