Rank, 14 days

2 people reported

All time, since Oct 26.

Bun check reports TS2322 tsc accepts on deeply nested types

“Possibly the same cause as #46998 (deep comparisons are cut off at different depths than tsc).”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/bun/issues/21687/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Deep comparisons are cut off at different depths than tsc, giving false TS2322s and a missed one.

Is this your bug?

Where: bun check
Versions: 1.4.4. Still reported on the newest version, 1.4.4.
Platforms: macOS
How bad: Breaks a normal workflow.

Not quite your bug?

Type checking differs from 7.0.21 person
Check reports TS2615 unlike tsc2 people
Mapped NoInfer tuple rejected1 person

Original reports2, newest first

Oct 27, 2026bun check 1.4.4: TS2322 on a @hono/zod-openapi handler whose response type is 4 arrays deep (tsc 7.0.2, 7.1.0-beta and bun 1.4.3 accept)#47051
Oct 26, 2026bun check: deep comparisons are cut off at different depths than tsc (false TS2322s and a missed one)#46998

Do you work on Bun?

Claim its RAP Sheet to see what your users report and answer them in one place.