Recordsnpmsocket.io-client
Compatibility cube
Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.
| socket.io-client | Manager | Socket.emitWithAck | Socket.onAny | WebSocketServer shared ×2 | io | socket.io-client.Manager | socket.io-client.io | |
|---|---|---|---|---|---|---|---|---|
| 4.8.3 | 100%5 | 100%1 | 100%1 | 100%2 | 100%1 | 100%1 | ||
| 4.8.1 | 65%26 | — | — | 100%1 | 100%1 |
Showing the environments with the most evidence.
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
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.