Recordsnpm@babel/corefailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
test_contract.go:<n>:<n>: no required module provides package golang.org/x/text/unicode/norm: go.mod file not found in current directory or any parent …
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-05 · Last seen: 2026-09-05
sha256:15e1b71df43a…
@babel/core.default
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 8.0.1 not measured
- 8.0.0-rc.6 FAIL
- 7.29.7 not measured
- 7.29.6 not measured
- 7.28.5 not measured
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-09-05 → 2026-09-05
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 8.0.1 | 8.0.0-rc.6 | 7.29.7 | 7.29.6 | 7.28.5 |
|---|---|---|---|---|---|
| @babel/code-frame | 8.0.0 | 8.0.0 | 7.29.7 | 7.29.7 | 7.27.1 |
| @babel/generator | 8.0.0 | 8.0.0 | 7.29.7 | 7.29.8 | 7.28.5 |
| @babel/helper-compilation-targets | 8.0.0 | 8.0.0 | 7.29.7 | 7.29.7 | 7.27.2 |
| @babel/helper-module-transforms | — | — | 7.29.7 | 7.29.7 | 7.28.3 |
| @babel/helpers | 8.0.0 | 8.0.0 | 7.29.7 | 7.29.7 | 7.28.4 |
| @babel/parser | 8.0.4 | 8.0.4 | 7.29.7 | 7.29.8 | 7.28.5 |
| @babel/template | 8.0.0 | 8.0.0 | 7.29.7 | 7.29.7 | 7.27.2 |
| @babel/traverse | 8.0.4 | 8.0.4 | 7.29.7 | 7.29.8 | 7.28.5 |
| @babel/types | 8.0.4 | 8.0.4 | 7.29.7 | 7.29.8 | 7.28.5 |
| semver | 7.8.5 | 7.8.5 | 6.3.1 | 6.3.1 | 6.3.1 |
| @babel/preset-env | — | — | 7.29.7 | — | — |
| @jridgewell/remapping | — | — | 2.3.5 | 2.3.5 | 2.3.5 |
| @types/gensync | 1.0.5 | 1.0.5 | — | — | — |
| convert-source-map | 2.0.0 | 2.0.0 | 2.0.0 | 2.0.0 | 2.0.0 |
| core-js | — | — | 3.50.0 | — | — |
| debug | — | — | 4.4.3 | 4.4.3 | 4.4.3 |
| empathic | 2.0.1 | — | — | — | — |
| find-up-simple | — | 1.0.1 | — | — | — |
| gensync | 1.0.0-beta.2 | 1.0.0-beta.2 | 1.0.0-beta.2 | 1.0.0-beta.2 | 1.0.0-beta.2 |
| import-meta-resolve | 4.2.0 | 4.2.0 | — | — | — |
| json5 | 2.2.3 | 2.2.3 | 2.2.3 | 2.2.3 | 2.2.3 |
| obug | 2.1.4 | 2.1.4 | — | — | — |
Moved: 10 · unchanged at every release: 12
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.