Recordsnpmlightningcss-linux-x64-gnufailure issue
Failure signature
PROJECT_TEST exit 1 ERR_ASSERTION ×1
AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: · 2 !== 0 · at TestContext.<anonymous> (<url>) …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · First recorded: 2026-09-13 · Last seen: 2026-09-13
sha256:0cab186a142b…
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.
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_TEST.
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- lightningcss-linux-x64-gnu 1.33.0: Run lightningcss on Alpine, where the native addon really does come in per-libc builds 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. HOWlightningcss.transformdetectLibc.familySynclightningcss-linux-x64-musllightningcss-linux-x64-gnunode 22 MIT-0 · 2026-08-14