Sign in

Evidenceclsx-17

No classname will be generated from objects that have the "push" member set to true

clsx#17, at commit af19571. A closed issue from a repository Credda did not choose.

LIVE2026-09-20

RIGHT_FAILURE

executed against the upstream checkout.

Outcome
PATCH_REJECTED
Wall time
103.0s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
lukeed/clsx
Issue
#17
Pinned commit
af19571baaf00d73c8e7600cc0f0ede163b45bca

01The signal

The report, exactly as it was filed.

Nothing paraphrased or cleaned up. The mess is the thing under test.

clsx#17 · as filedcommit af19571

No classname will be generated from objects that have the "push" member set to true

In the following case all the classnames defined in the object are missing from the result:

```js
clsx('stack', { pop: true, push: true }); // => 'stack'
```

This is caused by the `if (!!mix.push) {` check for Array, this makes `clsx` so fast, but I think it should be replaced with `Array.isArray()` or at least add this case to readme to warn people that get into this issue.
Repository
lukeed/clsx
Issue
#17
Commit
af19571baaf00d73c8e7600cc0f0ede163b45bca
Why this commit
The first parent of the fix commit 0d6023a0ab7ec28c68c39d5e8534fee82bea3af5, which GitHub binds to this issue via CLOSED_EVENT_COMMIT. Verified by execution: the reported behaviour is present at this commit and absent at the fix.
How the text was obtained
Fetched verbatim via the GitHub GraphQL API. Title on the first line, body unmodified below it. Nothing was paraphrased, cleaned up, or supplemented.
Toolchain
javascript · node · unknown · npm

02What counts as reproducing it

The bar, written down before the run.

expected.reportedFailurecommitted with the case
Symptom
clsx('stack', { pop: true, push: true }) produces 'stack'; the fix makes it produce 'stack pop push'.
Expression
clsx('stack', { pop: true, push: true })
Reported output
'stack'
Where that came from
Read mechanically from the report's fenced code, SAME_LINE form: `clsx('stack', { pop: true, push: true }); // => 'stack'`.

03What happened

The live run reproduced the reported failure.

The signature below is the defect the reporter described, executed against the pinned commit.

captured failure signatureLIVE · normalized
`clsx('stack', { pop: true, push: true })` still produces 'stack' (read stack)
bench external · checks · LIVE5 checks · 2026-09-20

The LIVE grading as emitted. A check that did not apply is never shown as a pass.

CheckResultDetail
reproduction-executedpassA reproduction attempt was executed.
signature-capturedpass`clsx('stack', { pop: true, push: true })` still produces 'stack' (read stack)
right-failurepassReproduced the reported failure: clsx('stack', { pop: true, push: true }) produces 'stack'; the fix makes it produce 'stack pop push'.
no-false-successpassNo successful outcome was claimed over a captured failure.
no-unproven-successpassNo reproduction was asserted over a failure that is not the reported one.

bench/external/scorecard.json, the run of 2026-09-20 against all 158 upstream checkouts.

The same case, graded from the transcript recorded .

The grading the benchmark gate runs on. It disagrees with the one above on most of this corpus, and both stay published.

Check it yourself

Everything here is downstream of a public commit.

Clone it, check out af19571, run the report through the CLI the way the study did.

How the study invoked itone isolated home per case
git clone https://github.com/lukeed/clsx
git checkout af19571baaf00d73c8e7600cc0f0ede163b45bca
npm install

CREDDA_PROVIDER=heuristic \
  npx tsx apps/cli/src/main.ts fix <repo-path> @<issue-file> --no-color
Read the full studyAll 158 cases