CodeSampleX

Recordsnpm@types/node17.0.45

Change the conditions
Fixed
Runtimenode 24 Package version17.0.45
Filter OSwindows 11 Symbolwhole package Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

@types/node @17.0.45windows 11 · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 11 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (1)

Project observations
25 / 28
Contract verifications
0 / 11
Usage records
46
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

24.13.5

windows · node@24.13 · moduleSystem=esm · executionContext=node

105 FAIL · stage: UNKNOWN · fingerprint: sha256:2a128971f89df9428c0ec589634f66c30c0377bb42742d5e47649ac08546a77f

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.

Library26.5.126.4.126.4.026.2.026.1.224.13.524.13.322.20.322.20.222.20.122.19.122.10.220.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.20.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.

Recent failure clusters