Exemplo

Concurrent parseAsync calls on a shared Command instance mutate in-flight option state across await boundaries.

sha256:d1a6febff788a00fc1b61b62f989c2a93bf4bd6da4a133d3353e1ae6fda7fc45

Caso

Objetivo

Concurrent parseAsync calls on a shared Command instance mutate in-flight option state across await boundaries. HOW

Pacotes

commander 13.1.0

Ambiente

node

Criado

2026-08-17T01:48:44Z

O que costuma-se supor

Parsing multiple command invocations concurrently with parseAsync on a shared Command instance keeps options isolated within each execution promise.

O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.

Contrato

• 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.

Arquivos

• NOTES.md
• csx.json
• package-lock.json
• package.json
• src/index.mjs
• test/contract.mjs

Baixar o artefato verificado (tar.gz) — exatamente os bytes contra os quais o contrato rodou

Seeder de origem

csx-seed

Recibos de verificação

• node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9