Recordsnpmlightningcss-linux-x64-muslfailure issue
Failure signature
PROJECT_TEST exit 1 ERR_LOAD_URL ×1
Contract test failed: Error: Failed to load custom Reporter from basic · at loadCustomReporterModule (fil<path>:<n>:<n>) · at fil<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:a60e7101af87…
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=linux · runtime=node@22.23 ×1 2026-08-31 → 2026-08-31
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 1.32.0 → first failing release 1.33.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- lightningcss-linux-x64-musl 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