Recordsgolanggolang.org/x/xerrorsfailure issue
Failure signature
PROJECT_PROCESS exit 1 ERR_MODULE_NOT_FOUND ×1
node:internal/modules/package_json_reader:<n> · throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); · ^ …
Evidence quality: complete · First recorded: 2026-08-29 · Last seen: 2026-08-29
sha256:c33691aec18d…
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.
- v0.0.0-20200804184101-5ec99f83aff1 FAIL
- v0.0.0-20191204190536-9bdfabe68543 PASS 43 passing observations
- v0.0.0-20191011141410-1b5146add898 PASS 19 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-29 → 2026-08-29
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 v0.0.0-20191204190536-9bdfabe68543 → first failing release v0.0.0-20200804184101-5ec99f83aff1
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
- golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1: xerrors error wrapping and chain inspection with Errorf and Is 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. HOWxerrors.Errorfxerrors.Is MIT-0 · 2026-08-27