Sample
Option.implies() in Commander 10.0.1 accepts a string option name to set boolean flags without decomposing the string into numeric indices as in Commander 10.0.0
sha256:997e08319af13c6ed363d7ec20d7adfe1887d84969fab414a089a8f815cf9f19
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Option.implies() in Commander 10.0.1 accepts a string option name to set boolean flags without decomposing the string into numeric indices as in Commander 10.0.0 HOW
- Packages
- commander 10.0.1
- Environment
- node
- Created
- 2026-08-16T17:52:05Z
Commonly assumed
Passing a string option name to Option.implies() sets that option to true when the triggering option is parsed.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Option.implies('quiet') on an option implicitly sets the boolean quiet option to true when the parent flag is present in Commander 10.0.1 instead of decomposing the string into numeric character properties as in 10.0.0
- opts().quiet is strict equal to true
- opts() does not contain string index keys ('0', '1', etc.)
- omitting the triggering option leaves implied options undefined
- direct --quiet flag sets quiet option independently
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