Recordsnpm@babel/core
there is a sample for this release and API (9)
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
How to read the grid
Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.
Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
7.26.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
5 FAIL
· stage: UNKNOWN
· fingerprint: sha256:91ad26545eb1f3df29e3d9731c4244f3cf919942db2aa314b6b8d67ca84b47ef
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @babel/code-frame | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/generator | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/helper-compilation-targets | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/helper-module-transforms | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/helpers | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/parser | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/template | 7.29.7 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/traverse | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @babel/types | 7.29.8 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| convert-source-map | 2.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| semver | 6.3.1 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| @ampproject/remapping | 2.3.0 | PASS All observations passed | contract passed | 19 project-days |
| debug | 4.4.3 | PASS All observations passed | contract passed | 19 project-days |
| gensync | 1.0.0-beta.2 | PASS All observations passed | contract passed | 19 project-days |
| json5 | 2.2.3 | PASS All observations passed | contract passed | 19 project-days |
The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.
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.
Moved: 11 · 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.