Recordsnpmrobots-parserfailure issue
Failure signature
PROJECT_COMPILE exit 1 TS7034 ×1
tests/crawl-budget.test.ts(<n>,<n>): error TS7034: Variable <str> implicitly has type <str> in some locations where its type cannot be determined.
Evidence quality: complete · typescript/tsc · compiler-diagnostic · outer npm run · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:85a890982324…
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.
- 3.0.1 FAIL
Where it reproduced
- executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×1 2026-09-13 → 2026-09-13
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- robots-parser 3.0.1: robotsParser 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. HOWrobotsParser MIT-0 · 2026-09-13
- robots-parser 3.0.1: isAllowed 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. HOWisAllowed MIT-0 · 2026-09-13
- robots-parser 3.0.1: getCrawlDelay 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. HOWgetCrawlDelay MIT-0 · 2026-09-13