Recordsnpmfast-urifailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×2
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · <str> !== <str> · at <url> …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-10-19 · Last seen: 2026-10-19
sha256:030f880b3a09…
fast-uri.equal fast-uri.normalize fast-uri.parse fast-uri.resolve fast-uri.resolveComponent fast-uri.serialize
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.2.3 not measured
- 4.2.2 FAIL
- 4.1.2 PASS 2 passing observations
- 3.1.9 PASS 21 passing observations
- 3.1.8 PASS 9 passing observations
Where it reproduced
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×2 2026-10-19 → 2026-10-19
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 passing release 4.1.2 → first failing release 4.2.2
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- fast-uri 4.2.2 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. HOW MIT-0 · 2026-10-19