Adapter to enable uni casting of events to multiple separate socket.io server nodes.
active 2023-08-16 → 2026-02-09 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 909 days from 2023-08-16 to 2026-02-09. Pushes: 11 total, peak 8 in a day. Pull requests: 19 total, peak 4 in a day. Issues: 62 total, peak 4 in a day. Comments: 118 total, peak 10 in a day. Stars: 120 total, peak 2 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| darrachequesne | 58 | 11 | 5 | 35 |
| MartinKolarik | 15 | 0 | 3 | 7 |
| cody-evaluate | 8 | 0 | 0 | 7 |
| knixer | 5 | 0 | 0 | 2 |
| hysapp | 5 | 0 | 0 | 3 |
| zishang520 | 5 | 0 | 2 | 1 |
| LokeshDaga | 4 | 0 | 0 | 1 |
| Valentinfe | 4 | 0 | 0 | 2 |
| nwalters512 | 4 | 0 | 0 | 2 |
| dr-js | 4 | 0 | 1 | 3 |
| introspection3 | 4 | 0 | 0 | 4 |
| techsin | 3 | 0 | 0 | 1 |
| gaetansenn | 3 | 0 | 0 | 1 |
| sordu | 3 | 0 | 0 | 1 |
| Daniel-kekeke | 3 | 0 | 0 | 0 |
| jlippold | 3 | 0 | 0 | 2 |
| RoccoC | 3 | 0 | 1 | 1 |
| MatanYemini | 3 | 0 | 0 | 2 |
| yuangao0317 | 3 | 0 | 0 | 1 |
| shivashahu07 | 3 | 0 | 0 | 2 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#571darrachequesne2026-02-09 16:09There is no sSubscribe method on redisClient object when using redis sentinel with node-redis
- Issue comment#570darrachequesne2026-01-20 18:02feat: add support for ioredis Cluster with Sharded Pub/Sub
- Issue#571barisusakli2026-01-20 16:13There is no sSubscribe method on redisClient object when using redis sentinel with node-redis
- Pull request#570seta-chuang-09092026-01-12 03:26
- Pull request#569anushka18222026-01-08 10:22
- Issue#566cherviakovtaskworld2026-01-02 04:24Is this project maintained?
- Issue#565yunho-microsoft2025-10-22 20:32Reason of using psub in redis adapter's broadcast function?
- Pull request#562doganbulut2025-05-23 10:29
- Pull request#562doganbulut2025-05-23 10:27
- Issue#559ubidval2025-04-07 14:29Compatibility with Valkey
- Issue comment#559ubidval2025-04-07 14:29Compatibility with Valkey
- Issue#561maitrungduc14102025-04-05 14:57[Bug]: sharded pubsub uses wrong channel after joining a room
- Issue comment#510maitrungduc14102025-04-05 10:23How scalable is the redis pub/sub approach?
- Issue comment#559darrachequesne2025-03-28 07:37Compatibility with Valkey
- Issue#560sivakumar-742025-03-24 17:33How to Disconnect a Socket ID in Multi-Server Environment with Redis Streams Adapter
- Issue comment#558zhangkai8032025-03-19 08:19AUTH command have been sent too many times
- Issue#558zhangkai8032025-03-19 08:11AUTH command have been sent too many times
- Issue comment#367HannaSamia2025-03-11 13:53Error: timeout reached while waiting for sockets response
- Issue#557dizzyjaguar2025-03-06 17:04io.fetchSockets() sometimes works across instances, sometimes not
- Issue comment#544dizzyjaguar2025-03-06 16:57io.in(`${roomId}`).fetchSockets() sometimes cannot get socket from other server
- Issue comment#522cherviakovtaskworld2025-02-21 02:46Error: 23984 trailing bytes
- Issue comment#504kucukaslan2025-02-13 13:23Unclear documentation around "channels"
- Issue comment#553jlippold2025-02-10 00:19Is elasticache cluster mode supported with node-redis?
- Issue comment#553ollie54632025-02-07 13:47Is elasticache cluster mode supported with node-redis?
- Issue comment#553darrachequesne2025-01-07 11:04Is elasticache cluster mode supported with node-redis?
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 120 stars here means stars gained during the window, not the repo's star count.