Recordsnpmsocket.io-client
Change the conditions
Current conditions
Manager @4.8.3musl · x64 · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and our run of it at this coordinate came back clean (1)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-18
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
windows 11 · x64 · node 24 · npm 11 · node
1 of 1 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
4.8.1
linux · node@22.23 · moduleSystem=cjs · executionContext=node
9 FAIL · stage: PROJECT_PROCESS
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 | 4.8.3 | 4.8.1 |
|---|---|---|
| debug | 4.4.3 | 4.3.7 |
| @socket.io/component-emitter | 3.1.2 | 3.1.2 |
| engine.io-client | 6.6.6 | 6.6.6 |
| socket.io-parser | 4.2.7 | 4.2.7 |
| ws | 8.21.3 | — |
Moved: 1 · unchanged at every release: 4
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.