CodeSampleX

Recordsnpmsocket.io-client4.8.1socket.io-client.Manager

Change the conditions
Fixed
Package version4.8.1 Symbolsocket.io-client.Manager
Filter OSwindows 11 Runtimenode 24 Architecturex64 Package managernpm 11 Execution contextnode Clear filters

Current conditions

socket.io-client.Manager @4.8.1windows 11 · x64 · node 24 · npm 11 · node

1 of 1 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
1 / 1
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-08-19

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 3

First observed break

4.8.1

linux · node@22.23 · moduleSystem=cjs · executionContext=node

9 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
debug 4.3.7 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
@socket.io/component-emitter 3.1.2 PASS All observations passed contract passed 6 project-days
engine.io-client 6.6.6 PASS All observations passed contract passed 5 project-days
socket.io-parser 4.2.7 PASS All observations passed contract passed 4 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: 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.