Recordsnpmesbuildfailure issue
Failure signature
PROJECT_PROCESS EFTYPE Evidence gap ×11
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-11-04 · Last seen: 2026-11-04
esbuild.buildSync
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.
- 0.28.2 PASS 53 passing observations
- 0.28.1 FAIL
- 0.27.2 PASS 11 passing observations
- 0.25.12 PASS 35 passing observations
- 0.25.0 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×11 2026-11-04 → 2026-11-04
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 0.27.2 → first failing release 0.28.1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release 0.28.1 → first passing release 0.28.2
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.
- Releases in this window never measured at PROJECT_PROCESS: 1
- No resolved dependency tree for 0.27.2 or for 0.28.1, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- esbuild 0.28.1 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. HOWnode 22.23.2 MIT-0 · 2026-08-20