Export interface changed (jest)

[artur-ma]

Not sure what happened, but after upgrading to ioredis@4.27.10
jest cant fully mock ioredis module

ioredis@4.27.10

> jest.genMockFromModule('ioredis').Cluster
undefined

ioredis@4.27.9

> jest.genMockFromModule('ioredis').Cluster
ƒ Cluster() {return mockConstructor.apply(this,arguments);}

[luin]

4.27.10 doesn't seem to introduce any changes that can affect this: v4.27.9...v4.27.10

[artur-ma]

@luin yeah, I saw the diff, I dont know what is the reason
u can look on the isolated example prepared by me

https://github.com/artur-ma/ioredis-bug/tree/main

[artur-ma]

I think its related to the version of typescript u used for version x.10

this is x.10 index.js

var cluster_1 = require("./cluster");
Object.defineProperty(exports, "Cluster", { enumerable: true, get: function () { return cluster_1.default; } });

this is x.9

var cluster_1 = require("./cluster");
exports.Cluster = cluster_1.default;

[liaoliaots]

same issue ✿◡‿◡

[liaoliaots]

@artur-ma
Because jest automock does not mock getters and setters.

But we can mock manually via:

// __mocks__/ioredis.ts
import { Cluster, Redis } from 'ioredis';

const mockIORedis = jest.createMockFromModule<{ default: Redis }>('ioredis/built/redis').default;
Reflect.defineProperty(mockIORedis, 'Cluster', {
    enumerable: true,
    value: jest.createMockFromModule<{ default: Cluster }>('ioredis/built/cluster').default
});

export default mockIORedis;

[artur-ma]

Hey, thanks, but the point that this is a breaking change, we have hundreds on tests that rely on these mocks :(

[luin]

@artur-ma You are correct. Sorry for didn't notice that. Created a fix!
@liaoliaots Thanks for the solution here.

[ioredis-robot]

🎉 This issue has been resolved in version 4.27.11 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀