Recordsnpmwsfailure issue
Failure signature
PROJECT_TEST exit 1 EOF ×1
[31m[1mAssertionError[22m: expected [ <str>, <str>, <str>, <str> ] to deeply equal [ <str>, <str>, <str>, <str> ][39m · [32m- Expected[39m …
Evidence quality: complete · javascript/test-runner · test-runner-diagnostic · outer npm test · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:d757efcbaf88…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 8.21.3 PASS 12 passing observations
- 8.21.1 FAIL
- 8.21.0 PASS 1 passing observations
- 8.18.3 PASS 1 passing observations
- 8.18.0 PASS 3 passing observations
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=windows · runtime=node@24.13 ×1 2026-09-15 → 2026-09-15
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 8.21.0 → first failing release 8.21.1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release 8.21.1 → first passing release 8.21.3
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No resolved dependency tree for 8.21.0 or for 8.21.1, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- ws 8.21.1: WebSocket.createWebSocketStream This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWWebSocket.createWebSocketStreamnode 22.23.2 MIT-0 · 2026-09-01
- ws 8.21.1: WebSocketServer.handleUpgrade This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWWebSocketServer.handleUpgrade MIT-0 · 2026-08-30
- ws 8.21.1: Route multiple WebSocket endpoints on a single HTTP server using WebSocketServer noServer and handleUpgrade This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWWebSocketServerWebSocketServer.prototype.handleUpgradenode 22 MIT-0 · 2026-08-28