Recordsnpm@nodable/entitiesfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
[31m[1mAssertionError[22m: expected <str> to match <path>:prism-source-news-ycombinato…/[39m · [32m- Expected:[39m …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-09 · Last seen: 2026-09-09
sha256:77545ab83bf9…
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.
- 3.0.0 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-09 → 2026-09-09
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_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- @nodable/entities 3.0.0: EntityDecoder, EntityEncoder 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. HOWEntityDecoderEntityEncodernode 22.23.2 MIT-0 · 2026-08-24