Recordsnpmregjsparserfailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×2
throw new AssertionError(obj); · ^ · AssertionError [ERR_ASSERTION]: unterminated character class throws SyntaxError · at Object.<anonymous> (<path>:<n>:<n>)
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:f44234a16a10…
regjsparser.parse
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.
- 0.13.2 FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×2 2026-08-31 → 2026-08-31
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
- regjsparser 0.13.2: 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. HOWregjsparser.parsenode 22.23.2 MIT-0 · 2026-08-27