Records/npm/esbuild/failure issue

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.28.2 PASS 77 passing observations
• 0.28.1 PASS 2 passing observations
• 0.27.2 PASS 1 passing observations
• 0.25.12 FAIL
• 0.25.0 PASS 1 passing observations
• 0.21.5 PASS 34 passing observations

Where it reproduced

• executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 ×10 2026-08-29 → 2026-09-01

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.25.0 → first failing release 0.25.12

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release 0.25.12 → first passing release 0.27.2

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

Evidence gaps

• No resolved dependency tree for 0.25.0 or for 0.25.12, 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.25.12 Built ? 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. HOW MIT-0 · 2026-08-21
• esbuild 0.25.12: Run esbuild on Alpine, where the usual advice is to install a musl-specific build Built ? 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. HOWesbuild.transform@esbuild/linux-x64node 22 MIT-0 · 2026-08-14