Recordsnpmlightningcss-linux-x64-gnufailure issue
Failure signature
PROJECT_PROCESS ERR_MODULE_NOT_FOUND Evidence gap ×3
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-14 · Last seen: 2026-08-14
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS 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 ×3 2026-08-14 → 2026-08-14
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- 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