Recordsnpm@types/node26.2.0
Change the conditions
Current conditions
@types/node @26.2.0debian glibc · x64 · node 22 · npm · chrome 134
package-level total, not an API
Recorded as present in projects. Nothing was run at this coordinate.
Observed — real project builds reported from this coordinate.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-07
Dependency Health
Observed combinations and failure evidence for this release
First observed break
26.2.0
executionContext=node
16 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| undici-types | 8.3.0 | CANDIDATE Correlated change; unproven combination | contract passed | 28 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.
| Library | 26.5.1 | 26.4.1 | 26.4.0 | 26.2.0 | 26.1.2 | 24.13.5 | 24.13.3 | 22.20.3 | 22.20.2 | 22.20.1 | 22.19.1 | 20.19.43 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| undici-types | 8.9.0 | 8.3.0 | 8.3.0 | 8.3.0 | 8.3.0 | 7.18.2 | 7.18.2 | 6.21.0 | 6.21.0 | 6.21.0 | 6.21.0 | 6.21.0 |
Moved: 1 · unchanged at every release: 0
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.