Ejemplo
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
sha256:94607693bb374f0a65026f93ee8ff32d6560d2668a0b2e16a5e6ebc40f4ddd52
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- 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 HOW
- Paquetes
- commander 13.1.0
- Entorno
- node
- Creado
- 2026-08-16T16:19:04Z
Lo que suele suponerse
Throwing InvalidArgumentError from a custom option parser causes exitOverride to rethrow the InvalidArgumentError instance, while throwing standard JavaScript Error instances is caught and formatted as a CommanderError.
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- 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.
Archivos
- NOTES.md
- csx.json
- package-lock.json
- package.json
- src/index.mjs
- test/contract.mjs
Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato
Seeder de origen
Recibos de verificación
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-16 · ed25519:d91480838ac982c9