Recordsnpmcontent-typefailure issue
Failure signature
PROJECT_COMPILE exit 1 TS7005 ×2
tests/crawl-budget.test.ts(<n>,<n>): error TS7005: Variable <str> implicitly has an <str> type.
Evidence quality: complete · typescript/tsc · compiler-diagnostic · outer npm run · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:9157cca40f14…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×2 2026-09-13 → 2026-09-13
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 1.0.5 → first passing release 2.0.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 2.0.0 → first failing release 2.1.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- content-type 2.1.0: contentType.format, contentType.parse This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcontentType.formatcontentType.parse MIT-0 · 2026-08-18
- content-type 1.0.5: parse and format HTTP Content-Type header with parameters This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWcontentType.formatcontentType.parse MIT-0 · 2026-08-18