Cannot read property 'on' of undefined

[fliespl]

Version: 6.0.1

I am curious if documentation is still valid, cause example from it fails immediately.

const redisAdapter = require('socket.io-redis')({'host': '127.0.0.1', 'port': 6379});

redisAdapter.pubClient.on('error', function(){});
redisAdapter.subClient.on('error', function(){});

redisAdapter.pubClient.on('error', function(){});
                       ^

TypeError: Cannot read property 'on' of undefined
    at Object.<anonymous> (E:\Workspace\web\sf5\socket\server.js:6:24)

[cinout]

I encountered a similar issue. Have you found a solution to this issue @fliespl ?

I used TS way to create my redisAdapter, the code snippet is here:

import { RedisClient } from "redis";
import { createAdapter } from "socket.io-redis";

const pubClient = new RedisClient({ host:hostName, port: portNum});
const subClient = pubClient.duplicate();

const redisAdapter = createAdapter({
      pubClient,
      subClient,
    });

Then if I do console.log( redisAdapter.pubClient ), the output is undefined.

[fliespl]

@cinout yes, I did it like that.

Hooked events on custom defined sub/pubClient without going through redisAdapter.pubClient.

const pubClient = redis.createClient(6379, '127.0.0.1');
const subClient = pubClient.duplicate();

const redisAdapter = require('socket.io-redis').createAdapter({pubClient: pubClient, subClient: subClient})

pubClient.on('error', (err) => {
    console.log(err);
})
subClient.on('error', (err) => {
    console.log(err);
})

[cinout]

@cinout yes, I did it like that.

Hooked events on custom defined sub/pubClient without going through redisAdapter.pubClient.

const pubClient = redis.createClient(6379, '127.0.0.1');
const subClient = pubClient.duplicate();

const redisAdapter = require('socket.io-redis').createAdapter({pubClient: pubClient, subClient: subClient})

pubClient.on('error', (err) => {
    console.log(err);
})
subClient.on('error', (err) => {
    console.log(err);
})

@fliespl That works. Thank you for the help!

[darrachequesne]

Arf, that is indeed a change in the latest release that wasn't updated in the documentation, sorry for that.

I think the best way for now is to provide your own redis clients, as suggested above.