Rebridge somehow steals context of "this" about rebridge

[CapacitorSet]

I can't reproduce this. Can you include your options for Redis and Rebridge - or alternatively, a minimal but complete example that errors?

I used this file, with Rebridge 2.3.0:

const Redis = require("redis");
const Rebridge = require("rebridge");

class KnifeBot {
    constructor(config) {
        this.redis = Redis.createClient(config.redisOptions);
        this.db = new Rebridge(this.redis, config.rebridgeOptions);
    }

    pickGame() {
        return "Hey";
    }

    setGame() {
        let game = this.pickGame() // This line errors
        console.log(game);
    }
}

const bot = new KnifeBot({
    redisOptions: {},
    rebridgeOptions: {
        mode: "deasync"
    }
});
bot.setGame();

It works correctly by printing "Hey" to the console. It also works with mode: "promise" and without any Rebridge options.

[Ovyerus]

Both of my options for Redis and Rebridge aren't defined in my current config file, so undefined. Your example works fine for me, I'll create a stripped down version of my current implementation and see if it fails there.

[Ovyerus]

So it turns out that the this.pickGame is not a function error was caused because I was missing a config option, for some stupid reason. However console.log-ing still results in an error that points to Rebridge.

(It also seems that adding the console.log stops the first error from happening. Somehow.)

I've made a repo here which reproduces the errors.

[CapacitorSet]

Thank you, I'll work on it.

[CapacitorSet]

Ah, spotted it! That's a problem with your code, that doesn't depend on the usage of Rebridge. Indeed, if you try to remove all usages of Rebridge, you'll see that it still errors.

The problem is on this line (events/ready.js:23):

if (!bot.gameLoop) bot.gameLoop = setInterval(bot.setGame, bot.config.gameInterval);

What happens is that bot.setGame will not be called on the bot object, but on a Timeout object (specifically, the one returned by setInterval). This behaviour is documented here, and can be solved by using setTimeout(bot.setGame.bind(bot), ...) or more elegantly with setTimeout(() => bot.setGame(), ...).

[Ovyerus]

Huh, that's pretty weird behaviour. Thanks a lot for your help anyway! :)