Sample
commander 13.1.0: Distinguish Commander error paths where exitOverride intercepts InvalidArgumentError as a CommanderError instance with commander.invalidArgument code rather than preserving the InvalidArgumentError class or wrapping standard Error exceptions
Verified sample for npm commander 13.1.0: Distinguish Commander error paths where exitOverride intercepts InvalidArgumentError as a CommanderError instance…
sha256:94607693bb374f0a65026f93ee8ff32d6560d2668a0b2e16a5e6ebc40f4ddd52
This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured.
How many distinct signing keys filed a passing contract receipt. One is the author alone; more than one means somebody else built it too. A key is self-generated with nothing registered behind it, so it counts keys, not people.
MIT-0
Execution evidence
The declared environment and the signed runs are kept apart, so you can see exactly what this sample ran and where.
- Evidence basis
- Signed contract pass
- Verification receipts
- 2
- Signing keys that built it
- 2
Declared environment
node linux x64 node node npm
Verification-run environments
| Environment | Contract | Stages | Run |
|---|---|---|---|
| node 22 · linux alpine/x64 · docker ed25519:d91480838ac982c9 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-16 |
| node 22 · linux alpine/x64 · docker ed25519:2175b912ea1c23b1 | PASS | compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS CONTAINER_RUN · node-typescript@1 |
2026-08-18 |
Case
HOW- Goal
- Distinguish Commander error paths where exitOverride intercepts InvalidArgumentError as a CommanderError instance with commander.invalidArgument code rather than preserving the InvalidArgumentError class or wrapping standard Error exceptions
- Packages
- Symbols
-
- InvalidArgumentError
- CommanderError
- Command.prototype.exitOverride
- Command.prototype.option
- Command.prototype.requiredOption
- Option.prototype.choices
- Environment
- node
- Created
- 2026-08-16T16:19:04Z
Contract
- Throwing InvalidArgumentError inside a custom option parser causes exitOverride to throw a CommanderError instance where err instanceof InvalidArgumentError evaluates to false, err.code is 'commander.invalidArgument', and err.nestedError is undefined.
- Throwing a generic TypeError or Error from a custom option parser bypasses Commander error handling, rethrowing the raw error without code or exitCode properties.
- Invalid option choices trigger a CommanderError with code 'commander.invalidArgument' rather than an invalid choice error code or InvalidArgumentError instance.
- Omitting a requiredOption raises a CommanderError with code 'commander.missingMandatoryOptionValue' rather than 'commander.missingOption'.
- Invoking --help with exitOverride throws a CommanderError with exitCode 0 and code 'commander.helpDisplayed' rather than exiting cleanly or throwing an error code.
Files
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/index.mjs
- test/contract.mjs