Sign in

Evidencecheerio-116

add .toString() or JSON.stringify() support

cheerio#116, at commit 6d8ba33. 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
98.9s
Checks
5 passed of 5 applicable

RECORDED

NOT_GRADED

graded from the transcript committed with this case.

Outcome
not recorded
Checks
none run
Repository
cheeriojs/cheerio
Issue
#116
Pinned commit
6d8ba33b9d2c5581b1faa1046b1ac67f07acb057

01The signal

The report, exactly as it was filed.

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

cheerio#116 · as filedcommit 6d8ba33

add .toString() or JSON.stringify() support

it would be nice to do this:

``` javascript
var $ = require('cheerio')
var html = $('<div class="foo">bar</div>')
html.toString() // => '<div class="foo">bar</div>'
```

right now I can only call `.html()` on `html` which returns `foo`
Issue
#116
Commit
6d8ba33b9d2c5581b1faa1046b1ac67f07acb057
Why this commit
The first parent of the fix commit 3acc6f393fe9bf0df3b8822d7c04f6704ba369dd, which GitHub binds to this issue via CROSS_REFERENCED_PR. 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
($('<div class="foo">bar</div>')).toString() does not produce '<div class="foo">bar</div>'; the fix makes it do so.
Expression
($('<div class="foo">bar</div>')).toString()
Where that came from
Read mechanically from the report's fenced code, SAME_LINE form: `html.toString() // => '<div class="foo">bar</div>'`.

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
`html.toString()` still produces '<div class="foo">bar</div>' (read [object Object])
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`html.toString()` still produces '<div class="foo">bar</div>' (read [object Object])
right-failurepassReproduced the reported failure: ($('<div class="foo">bar</div>')).toString() does not produce '<div class="foo">bar</div>'; the fix makes it do so.
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 6d8ba33, 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/cheeriojs/cheerio
git checkout 6d8ba33b9d2c5581b1faa1046b1ac67f07acb057
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