Sample
Retrieve positional argument default values in Commander via processedArgs or action callbacks rather than program.args when arguments are unset
sha256:3fc59d6ae2df342949bb6f6c09dcdc027cda2183237046c0189f6cabfae569e9
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Retrieve positional argument default values in Commander via processedArgs or action callbacks rather than program.args when arguments are unset HOW
- Packages
- commander 13.1.0
- Environment
- node
- Created
- 2026-08-16T16:14:22Z
Commonly assumed
Configuring an optional argument with a default value populates program.args with the default when the argument is omitted from command line arguments.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- program.args remains empty when an optional positional argument with a default value is omitted, because default argument values are populated into program.processedArgs and action parameters rather than program.args.
- omitted defaulted argument is absent from program.args when partial arguments are supplied
- variadic omitted argument without an explicit default defaults to an empty Array rather than undefined
- custom coerce parser is bypassed for default values when options or arguments are omitted
- program.opts populates defaults for omitted options while program.args does not populate defaults for omitted arguments
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-16 · ed25519:d91480838ac982c9