Sample
Concurrent parseAsync calls on a shared Command instance mutate in-flight option state across await boundaries.
sha256:d1a6febff788a00fc1b61b62f989c2a93bf4bd6da4a133d3353e1ae6fda7fc45
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Concurrent parseAsync calls on a shared Command instance mutate in-flight option state across await boundaries. HOW
- Packages
- commander 13.1.0
- Environment
- node
- Created
- 2026-08-17T01:48:44Z
Commonly assumed
Parsing multiple command invocations concurrently with parseAsync on a shared Command instance keeps options isolated within each execution promise.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Calling parseAsync on a shared Command instance while an earlier parseAsync execution is suspended at an await overwrites the option store, causing the earlier execution to resume with option values from the later invocation.
- Option values retrieved via cmd.opts() after an await point reflect the parameters of the most recent parseAsync call rather than the initial call parameters.
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-17 · ed25519:d91480838ac982c9